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

nvmet-tcp: Fix potential UAF when ddgst mismatch

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 255 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.55% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 3 daysRemediation target: Within 90 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 255 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.

25 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.100-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1~deb12u1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.3-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.3-1Debian Security Tracker ↗Source updated 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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.

2 current
CVE-2026-64535 · CSAF 2.0 · revision 9 · interimSUSE Product Security TeamCVE-2026-64535
231 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-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros 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
Summary
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() - which performs percpu_ref_put() on the submission queue - but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done status == 0). It therefore calls nvmet_req_uninit() a second time on the same command - a double percpu_ref_put against a single percpu_ref_get.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64535 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: nvmet-tcp: Fix potential UAF when ddgst mismatch
235 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A use-after-free flaw was found in the Linux kernel's NVMe-over-Fabrics TCP target (nvmet-tcp) driver. When NVMe/TCP data digest is enabled and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based write transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit(), which drops a percpu_ref reference on the submission queue without marking the command as completed. During the subsequent queue teardown, the same command is treated as still needing data and nvmet_req_uninit() is called a second time, resulting in a double percpu_ref_put against a single percpu_ref_get. This use-after-free and reference-count underflow can crash the kernel (denial of service) when a remote NVMe/TCP initiator triggers a digest mismatch against a host configured as an NVMe/TCP target.
Remediation
There is no mitigation for this issue other than applying the kernel update once available. Because Red Hat does not support and does not enable the nvmet-tcp target functionality by default, systems that have not been explicitly configured with nvmetcli to act as an NVMe-over-Fabrics TCP target are not exposed and require no immediate action. Administrators who have deliberately configured an NVMe/TCP target using this unsupported functionality should restrict network access to the target port to trusted initiators on the same storage network only, and should consider disabling NVMe/TCP data digest or migrating off nvmet-tcp given its unmaintained status, until the fix is applied.
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-49113

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() — which performs percpu_ref_put() on the submission queue — but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done < transfer_len and cqe->status == 0). It therefore calls nvmet_req_uninit() a second time on the same command — a double percpu_ref_put against a single percpu_ref_get.

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
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 255 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: nvmet-tcp: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() — which performs percpu_ref_put() on the submission queue — but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done < transfer_len and cqe->status == 0). It therefore calls nvmet_req_uninit() a second time on the same command — a double percpu_ref_put against a single percpu_ref_get.

What

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() — which performs percpu_ref_put() on the submission queue — but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done < transfer_len and cqe->status == 0). It therefore calls nvmet_req_uninit() a second time on the same command — a double percpu_ref_put against a single percpu_ref_get.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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: nvmet-tcp: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() — which performs percpu_ref_put() on the submission queue — but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done < transfer_len and cqe->status == 0). It therefore calls nvmet_req_uninit() a second time on the same command — a double percpu_ref_put against a single percpu_ref_get.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-49113Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() — which performs percpu_ref_put() on the submission queue — but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done < transfer_len and cqe->status == 0). It therefore calls nvmet_req_uninit() a second time on the same command — a double percpu_ref_put against a single percpu_ref_get.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2527Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 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-64524 Référence CVE CVE-2026-64525 https://www.cve.org/CVERecord?id=CVE-2026-64525 Référence CVE CVE-2026-64526 https://www.cve.org/CVERecord?id=CVE-2026-64526 Référence CVE CVE-2026-64527 https://www.cve.org/CVERecord?id=CVE-2026-64527 Référence CVE CVE-2026-64528 https://www.cve.org/CVERecord?id=CVE-2026-64528 Référence CVE CVE-2026-64529 https://www.cve.org/CVERecord?id=CVE-2026-64529 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Référence CVE CVE-2026-64534 https://www.cve.org/CVERecord?id=CVE-2026-64534 Référence CVE CVE-2026-64535 https://www.cve.org/CVERecord?id=CVE-2026-64535 Référence CVE CVE-2026-64536 https://www.cve.org/CVERecord?id=CVE-2026-64536 Référence CVE CVE-2026-64541 https://www.cve.org/CVERecord?id=CVE-2026-64541 Référence CVE CVE-2026-64551 https://www.cve.org/CVERecord?id=CVE-2026-64551 Référence CVE CVE-2026-64556 https://www.cve.org/CVERecord?id=CVE-2026-64556 Référence CVE CVE-2026-64588 https://www.cve.org/CVERecord?id=CVE-2026-64588 Référence CVE CVE-2026-64589 https://www.cve.org/CVERecord?id=CVE-2026-64589 Référence CVE CVE-2026-64590 https://www.cve.org/CVERecord?id=CVE-2026-64590 Référence CVE CVE-2026-64591 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-64515 Référence CVE CVE-2026-64517 https://www.cve.org/CVERecord?id=CVE-2026-64517 Référence CVE CVE-2026-64518 https://www.cve.org/CVERecord?id=CVE-2026-64518 Référence CVE CVE-2026-64519 https://www.cve.org/CVERecord?id=CVE-2026-64519 Référence CVE CVE-2026-64524 https://www.cve.org/CVERecord?id=CVE-2026-64524 Référence CVE CVE-2026-64525 https://www.cve.org/CVERecord?id=CVE-2026-64525 Référence CVE CVE-2026-64526 https://www.cve.org/CVERecord?id=CVE-2026-64526 Référence CVE CVE-2026-64527 https://www.cve.org/CVERecord?id=CVE-2026-64527 Référence CVE CVE-2026-64534 https://www.cve.org/CVERecord?id=CVE-2026-64534 Référence CVE CVE-2026-64535 https://www.cve.org/CVERecord?id=CVE-2026-64535 Référence CVE CVE-2026-64536 https://www.cve.org/CVERecord?id=CVE-2026-64536 Référence CVE CVE-2026-64537 https://www.cve.org/CVERecord?id=CVE-2026-64537 Référence CVE CVE-2026-64538 https://www.cve.org/CVERecord?id=CVE-2026-64538 Référence CVE CVE-2026-64539 https://www.cve.org/CVERecord?id=CVE-2026-64539 Référence CVE CVE-2026-64540 https://www.cve.org/CVERecord?id=CVE-2026-64540 Référence CVE CVE-2026-64541 https://www.cve.org/CVERecord?id=CVE-2026-64541 Référence CVE CVE-2026-64542 https://www.cve.org/CVERecord?id=CVE-2026-64542 Référence CVE CVE-2026-64543 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-64524 Référence CVE CVE-2026-64525 https://www.cve.org/CVERecord?id=CVE-2026-64525 Référence CVE CVE-2026-64526 https://www.cve.org/CVERecord?id=CVE-2026-64526 Référence CVE CVE-2026-64527 https://www.cve.org/CVERecord?id=CVE-2026-64527 Référence CVE CVE-2026-64528 https://www.cve.org/CVERecord?id=CVE-2026-64528 Référence CVE CVE-2026-64529 https://www.cve.org/CVERecord?id=CVE-2026-64529 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Référence CVE CVE-2026-64534 https://www.cve.org/CVERecord?id=CVE-2026-64534 Référence CVE CVE-2026-64535 https://www.cve.org/CVERecord?id=CVE-2026-64535 Référence CVE CVE-2026-64536 https://www.cve.org/CVERecord?id=CVE-2026-64536 Référence CVE CVE-2026-64541 https://www.cve.org/CVERecord?id=CVE-2026-64541 Référence CVE CVE-2026-64551 https://www.cve.org/CVERecord?id=CVE-2026-64551 Référence CVE CVE-2026-64556 https://www.cve.org/CVERecord?id=CVE-2026-64556 Référence CVE CVE-2026-64587 https://www.cve.org/CVERecord?id=CVE-2026-64587 Référence CVE CVE-2026-64588 https://www.cve.org/CVERecord?id=CVE-2026-64588 Référence CVE CVE-2026-64589 https://www.cve.org/CVERecord?id=CVE-2026-64589 Référence CVE CVE-2026-64590 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-64512 Référence CVE CVE-2026-64513 https://www.cve.org/CVERecord?id=CVE-2026-64513 Référence CVE CVE-2026-64514 https://www.cve.org/CVERecord?id=CVE-2026-64514 Référence CVE CVE-2026-64518 https://www.cve.org/CVERecord?id=CVE-2026-64518 Référence CVE CVE-2026-64523 https://www.cve.org/CVERecord?id=CVE-2026-64523 Référence CVE CVE-2026-64529 https://www.cve.org/CVERecord?id=CVE-2026-64529 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Référence CVE CVE-2026-64534 https://www.cve.org/CVERecord?id=CVE-2026-64534 Référence CVE CVE-2026-64535 https://www.cve.org/CVERecord?id=CVE-2026-64535 Référence CVE CVE-2026-64536 https://www.cve.org/CVERecord?id=CVE-2026-64536 Référence CVE CVE-2026-64541 https://www.cve.org/CVERecord?id=CVE-2026-64541 Référence CVE CVE-2026-64548 https://www.cve.org/CVERecord?id=CVE-2026-64548 Référence CVE CVE-2026-64551 https://www.cve.org/CVERecord?id=CVE-2026-64551 Référence CVE CVE-2026-64552 https://www.cve.org/CVERecord?id=CVE-2026-64552 Référence CVE CVE-2026-64554 https://www.cve.org/CVERecord?id=CVE-2026-64554 Référence CVE CVE-2026-64555 https://www.cve.org/CVERecord?id=CVE-2026-64555 Référence CVE CVE-2026-64556 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64510 Référence CVE CVE-2026-64511 https://www.cve.org/CVERecord?id=CVE-2026-64511 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64514 https://www.cve.org/CVERecord?id=CVE-2026-64514 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Référence CVE CVE-2026-64532 https://www.cve.org/CVERecord?id=CVE-2026-64532 Référence CVE CVE-2026-64533 https://www.cve.org/CVERecord?id=CVE-2026-64533 Référence CVE CVE-2026-64534 https://www.cve.org/CVERecord?id=CVE-2026-64534 Référence CVE CVE-2026-64535 https://www.cve.org/CVERecord?id=CVE-2026-64535 Référence CVE CVE-2026-64536 https://www.cve.org/CVERecord?id=CVE-2026-64536 Référence CVE CVE-2026-64537 https://www.cve.org/CVERecord?id=CVE-2026-64537 Référence CVE CVE-2026-64538 https://www.cve.org/CVERecord?id=CVE-2026-64538 Référence CVE CVE-2026-64539 https://www.cve.org/CVERecord?id=CVE-2026-64539 Référence CVE CVE-2026-64540 https://www.cve.org/CVERecord?id=CVE-2026-64540 Référence CVE CVE-2026-64541 https://www.cve.org/CVERecord?id=CVE-2026-64541 Référence CVE CVE-2026-64542 https://www.cve.org/CVERecord?id=CVE-2026-64542 Référence CVE CVE-2026-64543 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64510 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64514 https://www.cve.org/CVERecord?id=CVE-2026-64514 Référence CVE CVE-2026-64529 https://www.cve.org/CVERecord?id=CVE-2026-64529 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Référence CVE CVE-2026-64532 https://www.cve.org/CVERecord?id=CVE-2026-64532 Référence CVE CVE-2026-64533 https://www.cve.org/CVERecord?id=CVE-2026-64533 Référence CVE CVE-2026-64534 https://www.cve.org/CVERecord?id=CVE-2026-64534 Référence CVE CVE-2026-64535 https://www.cve.org/CVERecord?id=CVE-2026-64535 Référence CVE CVE-2026-64536 https://www.cve.org/CVERecord?id=CVE-2026-64536 Référence CVE CVE-2026-64537 https://www.cve.org/CVERecord?id=CVE-2026-64537 Référence CVE CVE-2026-64538 https://www.cve.org/CVERecord?id=CVE-2026-64538 Référence CVE CVE-2026-64539 https://www.cve.org/CVERecord?id=CVE-2026-64539 Référence CVE CVE-2026-64540 https://www.cve.org/CVERecord?id=CVE-2026-64540 Référence CVE CVE-2026-64541 https://www.cve.org/CVERecord?id=CVE-2026-64541 Référence CVE CVE-2026-64544 https://www.cve.org/CVERecord?id=CVE-2026-64544 Référence CVE CVE-2026-64545 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64507 Référence CVE CVE-2026-64508 https://www.cve.org/CVERecord?id=CVE-2026-64508 Référence CVE CVE-2026-64509 https://www.cve.org/CVERecord?id=CVE-2026-64509 Référence CVE CVE-2026-64510 https://www.cve.org/CVERecord?id=CVE-2026-64510 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Référence CVE CVE-2026-64532 https://www.cve.org/CVERecord?id=CVE-2026-64532 Référence CVE CVE-2026-64533 https://www.cve.org/CVERecord?id=CVE-2026-64533 Référence CVE CVE-2026-64534 https://www.cve.org/CVERecord?id=CVE-2026-64534 Référence CVE CVE-2026-64535 https://www.cve.org/CVERecord?id=CVE-2026-64535 Référence CVE CVE-2026-64537 https://www.cve.org/CVERecord?id=CVE-2026-64537 Référence CVE CVE-2026-64538 https://www.cve.org/CVERecord?id=CVE-2026-64538 Référence CVE CVE-2026-64539 https://www.cve.org/CVERecord?id=CVE-2026-64539 Référence CVE CVE-2026-64540 https://www.cve.org/CVERecord?id=CVE-2026-64540 Référence CVE CVE-2026-64541 https://www.cve.org/CVERecord?id=CVE-2026-64541 Référence CVE CVE-2026-64542 https://www.cve.org/CVERecord?id=CVE-2026-64542 Référence CVE CVE-2026-64543 https://www.cve.org/CVERecord?id=CVE-2026-64543 Référence CVE CVE-2026-64544 https://www.cve.org/CVERecord?id=

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.12, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.97 ≤ 6.12.*, 6.18.40 ≤ 6.18.*, 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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 27 Jul 2026 · Last source change 19 Aug 2026, 16:28 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-49113
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 204 more
    After
    kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 205 more
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/dfb902462bca478f050224ec7a7195aafa7643b1; removed remediation: git.kernel.org/96fe2513df590e74b04253a45089cae75569570e.
    Before
    remediation: git.kernel.org/96fe2513df590e74b04253a45089cae75569570e
    After
    remediation: git.kernel.org/dfb902462bca478f050224ec7a7195aafa7643b1
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    fda871c0ba5d2eed2cd1c881573168129da70058 < 96fe2513df590e74b04253a45089cae75569570e; fda871c0ba5d2eed2cd1c881573168129da70058 < e091ff83d962f9ed00d9bd70443676de9fe98bdc; fda871c0ba5d2eed2cd1c881573168129da70058 < 6f9442983a3e4227afd1c83a5251ddbca585ea21; fda871c0ba5d2eed2cd1c881573168129da70058 < 088ee46c18d99baef453afd74181dd40ade044ad; fda871c0ba5d2eed2cd1c881573168129da70058 < dbbd07d0a7020b80f6a7028e561908f7b83b3d5a; 91edfca6f8b364d60cde3ddefaf7d03ddf35774b; 4b17476d809273617d3317fa0d4ae78aa488d760; 5.10.20 < 5.11 · Fixed: < 5.12; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1 ≤ *
    After
    91edfca6f8b364d60cde3ddefaf7d03ddf35774b < dfb902462bca478f050224ec7a7195aafa7643b1; fda871c0ba5d2eed2cd1c881573168129da70058 < 7e558308eba14c8136cb1e615f0c850f76d1fc0a; fda871c0ba5d2eed2cd1c881573168129da70058 < 96fe2513df590e74b04253a45089cae75569570e; fda871c0ba5d2eed2cd1c881573168129da70058 < e091ff83d962f9ed00d9bd70443676de9fe98bdc; fda871c0ba5d2eed2cd1c881573168129da70058 < 6f9442983a3e4227afd1c83a5251ddbca585ea21; fda871c0ba5d2eed2cd1c881573168129da70058 < 088ee46c18d99baef453afd74181dd40ade044ad; fda871c0ba5d2eed2cd1c881573168129da70058 < dbbd07d0a7020b80f6a7028e561908f7b83b3d5a; 4b17476d809273617d3317fa0d4ae78aa488d760 · Fixed: < 5.12; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1 ≤ *
    CNA ↗
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-49113↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-64535 · cve.blacktree.nl