BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-64121High confidence

net: ifb: report ethtool stats over num_tx_queues

Linux · Linux

7.1HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 19 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-64121 · CSAF 2.0 · revision 16 · interimSUSE Product Security TeamCVE-2026-64121
95 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • SUSE Linux Enterprise Live Patching 15 SP6:kernel-livepatch-6_4_0-150600_23_130-default
Summary
In the Linux kernel, the following vulnerability has been resolved: net: ifb: report ethtool stats over num_tx_queues ifb_dev_init() allocates dp->tx_private to dev->num_tx_queues entries via kzalloc_objs(*txp, dev->num_tx_queues). Both IFB per-queue RX and TX stats live in those entries: ifb_xmit() updates txp->rx_stats using the skb queue mapping, ifb_ri_tasklet() updates txp->tx_stats, and ifb_stats64() aggregates both over dev->num_tx_queues. The ethtool stats callbacks instead size and walk the per-queue stats with dev->real_num_rx_queues and dev->real_num_tx_queues. With an asymmetric device where the RX queue count exceeds the TX queue count, for example: ip link add name ifb10 numtxqueues 1 numrxqueues 8 type ifb ethtool -S ifb10 ifb_get_ethtool_stats() indexes past the tx_private allocation and copies adjacent slab data through ETHTOOL_GSTATS. Use dev->num_tx_queues consistently for the stats strings, the stats count, and the stats data walks. This reports one RX stats group and one TX stats group for each backing ifb_q_private entry, which is the queue set IFB can actually populate. Reproduced under UML+KASAN at v7.1-rc2: BUG: KASAN: slab-out-of-bounds in ifb_fill_stats_data+0x3c/0xae Read of size 8 at addr 0000000062dbd228 by task ethtool/36 ifb_fill_stats_data+0x3c/0xae ifb_get_ethtool_stats+0xc0/0x129 __dev_ethtool+0x1ca5/0x363c dev_ethtool+0x123/0x1b3 dev_ioctl+0x56c/0x744 sock_do_ioctl+0x15f/0x1b2 sock_ioctl+0x4d5/0x50a sys_ioctl+0xd8b/0xde9 With the patch applied, the same UML+KASAN repro is silent and ethtool -S ifb10 reports only the stats backed by the single allocated tx_private entry.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-45806

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: ifb: report ethtool stats over num_tx_queues ifb_dev_init() allocates dp->tx_private to dev->num_tx_queues entries via kzalloc_objs(*txp, dev->num_tx_queues). Both IFB per-queue RX and TX stats live in those entries: ifb_xmit() updates txp->rx_stats using the skb queue mapping, ifb_ri_tasklet() updates txp->tx_stats, and ifb_stats64() aggregates both over dev->num_tx_queues. The ethtool stats callbacks instead size and walk the per-queue stats with dev->real_num_rx_queues and dev->real_num_tx_queues. With an asymmetric device where the RX queue count exceeds the TX queue count, for example: ip link add name ifb10 numtxqueues 1 numrxqueues 8 type ifb ethtool -S ifb10 ifb_get_ethtool_stats() indexes past the tx_private allocation and copies adjacent slab data through ETHTOOL_GSTATS. Use dev->num_tx_queues consistently for the stats strings, the stats count, and the stats data walks. This reports one RX stats group and one TX stats group for each backing ifb_q_private entry, which is the queue set IFB can actually populate. Reproduced under UML+KASAN at v7.1-rc2: BUG: KASAN: slab-out-of-bounds in ifb_fill_stats_data+0x3c/0xae Read of size 8 at addr 0000000062dbd228 by task ethtool/36 ifb_fill_stats_data+0x3c/0xae ifb_get_ethtool_stats+0xc0/0x129 __dev_ethtool+0x1ca5/0x363c dev_ethtool+0x123/0x1b3 dev_ioctl+0x56c/0x744 sock_do_ioctl+0x15f/0x1b2 sock_ioctl+0x4d5/0x50a sys_ioctl+0xd8b/0xde9 With the patch applied, the same UML+KASAN repro is silent and ethtool -S ifb10 reports only the stats backed by the single allocated tx_private entry.

What

In the Linux kernel, the following vulnerability has been resolved: net: ifb: report ethtool stats over num_tx_queues ifb_dev_init() allocates dp->tx_private to dev->num_tx_queues entries via kzalloc_objs(*txp, dev->num_tx_queues). Both IFB per-queue RX and TX stats live in those entries: ifb_xmit() updates txp->rx_stats using the skb queue mapping, ifb_ri_tasklet() updates txp->tx_stats, and ifb_stats64() aggregates both over dev->num_tx_queues. The ethtool stats callbacks instead size and walk the per-queue stats with dev->real_num_rx_queues and dev->real_num_tx_queues. With an asymmetric device where the RX queue count exceeds the TX queue count, for example: ip link add name ifb10 numtxqueues 1 numrxqueues 8 type ifb ethtool -S ifb10 ifb_get_ethtool_stats() indexes past the tx_private allocation and copies adjacent slab data through ETHTOOL_GSTATS. Use dev->num_tx_queues consistently for the stats strings, the stats count, and the stats data walks. This reports one RX stats group and one TX stats group for each backing ifb_q_private entry, which is the queue set IFB can actually populate. Reproduced under UML+KASAN at v7.1-rc2: BUG: KASAN: slab-out-of-bounds in ifb_fill_stats_data+0x3c/0xae Read of size 8 at addr 0000000062dbd228 by task ethtool/36 ifb_fill_stats_data+0x3c/0xae ifb_get_ethtool_stats+0xc0/0x129 __dev_ethtool+0x1ca5/0x363c dev_ethtool+0x123/0x1b3 dev_ioctl+0x56c/0x744 sock_do_ioctl+0x15f/0x1b2 sock_ioctl+0x4d5/0x50a sys_ioctl+0xd8b/0xde9 With the patch applied, the same UML+KASAN repro is silent and ethtool -S ifb10 reports only the stats backed by the single allocated tx_private entry.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: net: ifb: report ethtool stats over num_tx_queues ifb_dev_init() allocates dp->tx_private to dev->num_tx_queues entries via kzalloc_objs(*txp, dev->num_tx_queues). Both IFB per-queue RX and TX stats live in those entries: ifb_xmit() updates txp->rx_stats using the skb queue mapping, ifb_ri_tasklet() updates txp->tx_stats, and ifb_stats64() aggregates both over dev->num_tx_queues. The ethtool stats callbacks instead size and walk the per-queue stats with dev->real_num_rx_queues and dev->real_num_tx_queues. With an asymmetric device where the RX queue count exceeds the TX queue count, for example: ip link add name ifb10 numtxqueues 1 numrxqueues 8 type ifb ethtool -S ifb10 ifb_get_ethtool_stats() indexes past the tx_private allocation and copies adjacent slab data through ETHTOOL_GSTATS. Use dev->num_tx_queues consistently for the stats strings, the stats count, and the stats data walks. This reports one RX stats group and one TX stats group for each backing ifb_q_private entry, which is the queue set IFB can actually populate. Reproduced under UML+KASAN at v7.1-rc2: BUG: KASAN: slab-out-of-bounds in ifb_fill_stats_data+0x3c/0xae Read of size 8 at addr 0000000062dbd228 by task ethtool/36 ifb_fill_stats_data+0x3c/0xae ifb_get_ethtool_stats+0xc0/0x129 __dev_ethtool+0x1ca5/0x363c dev_ethtool+0x123/0x1b3 dev_ioctl+0x56c/0x744 sock_do_ioctl+0x15f/0x1b2 sock_ioctl+0x4d5/0x50a sys_ioctl+0xd8b/0xde9 With the patch applied, the same UML+KASAN repro is silent and ethtool -S ifb10 reports only the stats backed by the single allocated tx_private entry.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Out-of-bounds Read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-125
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64105 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1202Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64098 Référence CVE CVE-2026-64099 https://www.cve.org/CVERecord?id=CVE-2026-64099 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64109 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1164Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64098 Référence CVE CVE-2026-64099 https://www.cve.org/CVERecord?id=CVE-2026-64099 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028286LinuxのLinux Kernelにおける境界外読み取りに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。net: ifb: num_tx_queuesを超えるethtool統計の報告に関する問題です。ifb_dev_init()はdp-＞tx_privateをdev-＞num_tx_queues分のエントリとしてkzalloc_objs(*txp, dev-＞num_tx_queues)で割り当てています。IFBの各キューごとのRXおよびTX統計情報はこれらのエントリ内に存在し、ifb_xmit()はskbのキュー対応付けを使ってtxp-＞rx_statsを更新します。ifb_ri_tasklet()はtxp-＞tx_statsを更新し、ifb_stats64()はdev-＞num_tx_queuesを基に両方を集約します。しかし、ethtoolの統計コールバックでは、デバイスのdev-＞real_num_rx_queuesおよびdev-＞real_num_tx_queuesを使ってパーキュー統計のサイズ計算や走査を行っていました。例えば、RXキュー数がTXキュー数を超える非対称デバイスにおいて、次のような環境があります。 ip link add name ifb10 numtxqueues 1 numrxqueues 8 type ifb ethtool -S ifb10この場合、ifb_get_ethtool_stats()がtx_privateの割り当て範囲を超えてインデックスアクセスし、ETHTOOL_GSTATSを通じて隣接するスラブ領域のデータをコピーしてしまいます。この問題を解決するために、統計情報の文字列やカウント、データ走査において一貫してdev-＞num_tx_queuesを使用するようにしました。これにより、IFBは実際に値を格納できるバックエンドのifb_q_privateエントリごとに、1つのRX統計グループと1つのTX統計グループを報告します。v7.1-rc2のUML+KASAN環境下で再現されていた状況は以下の通りです。 BUG: KASAN: slab-out-of-bounds in ifb_fill_stats_data+0x3c/0xae Read of size 8 at addr 0000000062dbd228 by task ethtool/36 ifb_fill_stats_data+0x3c/0xae ifb_get_ethtool_stats+0xc0/0x129 __dev_ethtool+0x1ca5/0x363c dev_ethtool+0x123/0x1b3 dev_ioctl+0x56c/0x744 sock_do_ioctl+0x15f/0x1b2 sock_ioctl+0x4d5/0x50a sys_ioctl+0xd8b/0xde9パッチ適用後は、同一のUML+KASAN再現環境でエラーが発生しなくなり、ethtool -S ifb10は単一の割り当て済みtx_privateエントリによってサポートされる統計情報のみを報告します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.17, 6.1.175 ≤ 6.1.*, 6.6.142 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 19 Jul 2026, 15:40 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-45806
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7; kernel-source as component of SUSE Linux Enterprise Module for Legacy 15 SP7; reiserfs-kmp-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7; kernel-default as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7; kernel-source as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7; kernel-default as component of SUSE Linux Enterprise Server 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Server 15 SP7; kernel-source as component of SUSE Linux Enterprise Server 15 SP7; reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP7; kernel-default as component of SUSE Linux Enterprise Server 16.0; kernel-devel as component of SUSE Linux Enterprise Server 16.0; kernel-macros as component of SUSE Linux Enterprise Server 16.0; kernel-source as component of SUSE Linux Enterprise Server 16.0; kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0; kernel-default as component of SUSE Linux Enterprise Server for SAP Applications 15 SP7; and 33 more
    After
    kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; SUSE Linux Enterprise Live Patching 15 SP6:kernel-livepatch-6_4_0-150600_23_130-default; SUSE Linux Enterprise Live Patching 15 SP6:kernel-livepatch-6_4_0-150600_23_92-default; kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_16-default; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_19-default; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_22-default; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_66-default; kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7; kernel-source as component of SUSE Linux Enterprise Module for Legacy 15 SP7; reiserfs-kmp-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7; kernel-default as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7; kernel-source as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7; kernel-default as component of SUSE Linux Enterprise Server 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Server 15 SP7; kernel-source as component of SUSE Linux Enterprise Server 15 SP7; reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP7; and 65 more
    SUSE Product Security Team ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-45806↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64121 · cve.blacktree.nl