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

xprtrdma: Fix bcall rep leak and unbounded peek

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 294 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.74% 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 294 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.100-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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-72466 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-72466
282 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
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Fix bcall rep leak and unbounded peek rpcrdma_is_bcall() decodes a reply's first words to decide whether the frame is a backchannel call. Two issues in that decode path let a short or malformed reply leak the receive buffer and drain the Receive queue. First, the speculative peek p = xdr_inline_decode(xdr, 0); /* five p++ reads follow */ asks xdr_inline_decode() for zero bytes, which returns xdr->p without consulting xdr->end. The five subsequent __be32 reads can then walk up to 20 bytes past the wire payload into stale regbuf contents and misclassify the reply as a backchannel call. Second, after the post-peek p = xdr_inline_decode(xdr, 3 * sizeof(*p)); if (unlikely(!p)) return true; the short-header arm returns true without calling rpcrdma_bc_receive_call(). The contract with the caller is that a true return transfers ownership of rep to the backchannel path: rpcrdma_reply_handler() if (rpcrdma_is_bcall(r_xprt, rep)) return; /* bare return, skips out_post */ ... out_post: rpcrdma_post_recvs(r_xprt, credits + ...); Because rpcrdma_bc_receive_call() never ran, no one took rep, but rpcrdma_reply_handler still bare-returns past rpcrdma_rep_put() and rpcrdma_post_recvs(). The rep, with its persistently DMA-mapped receive buffer, is orphaned on rb_all_reps and freed only at transport teardown. This completion reposts nothing, so its slot is reclaimed only when a later forward-channel reply reaches out_post and rpcrdma_post_recvs() allocates a fresh rep to backfill; absent that traffic the Receive queue drains and the peer's Sends draw RNR NAKs. Fix by consulting xdr->end after the zero-length peek so the five __be32 reads cannot run unless 20 bytes of wire payload remain. A byte-precise comparison against xdr->end is required because a non-4-aligned receive rounds the stream's word count up past the true payload. Also return false from the short-header arm so the reply falls through the normal out_norqst cleanup chain (rpcrdma_rep_put() plus rpcrdma_post_recvs()).
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-72466 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: xprtrdma: Fix bcall rep leak and unbounded peek
274 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 flaw was found in the Linux kernel's xprtrdma component. A remote attacker could exploit this vulnerability by sending a specially crafted, malformed reply. This could lead to a leak of the receive buffer and drain the Receive queue, potentially causing a Denial of Service (DoS) where the system becomes unresponsive to network requests.
Remediation
Fix deferred
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-59365

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

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 294 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: xprtrdma: Fix bcall rep leak and unbounded peek rpcrdma_is_bcall() decodes a reply's first words to decide whether the frame is a backchannel call. Two issues in that decode path let a short or malformed reply leak the receive buffer and drain the Receive queue. First, the speculative peek p = xdr_inline_decode(xdr, 0); /* five p++ reads follow */ asks xdr_inline_decode() for zero bytes, which returns xdr->p without consulting xdr->end. The five subsequent __be32 reads can then walk up to 20 bytes past the wire payload into stale regbuf contents and misclassify the reply as a backchannel call. Second, after the post-peek p = xdr_inline_decode(xdr, 3 * sizeof(*p)); if (unlikely(!p)) return true; the short-header arm returns true without calling rpcrdma_bc_receive_call(). The contract with the caller is that a true return transfers ownership of rep to the backchannel path: rpcrdma_reply_handler() if (rpcrdma_is_bcall(r_xprt, rep)) return; /* bare return, skips out_post */ ... out_post: rpcrdma_post_recvs(r_xprt, credits + ...); Because rpcrdma_bc_receive_call() never ran, no one took rep, but rpcrdma_reply_handler still bare-returns past rpcrdma_rep_put() and rpcrdma_post_recvs(). The rep, with its persistently DMA-mapped receive buffer, is orphaned on rb_all_reps and freed only at transport teardown. This completion reposts nothing, so its slot is reclaimed only when a later forward-channel reply reaches out_post and rpcrdma_post_recvs() allocates a fresh rep to backfill; absent that traffic the Receive queue drains and the peer's Sends draw RNR NAKs. Fix by consulting xdr->end after the zero-length peek so the five __be32 reads cannot run unless 20 bytes of wire payload remain. A byte-precise comparison against xdr->end is required because a non-4-aligned receive rounds the stream's word count up past the true payload. Also return false from the short-header arm so the reply falls through the normal out_norqst cleanup chain (rpcrdma_rep_put() plus rpcrdma_post_recvs()).

What

In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Fix bcall rep leak and unbounded peek rpcrdma_is_bcall() decodes a reply's first words to decide whether the frame is a backchannel call. Two issues in that decode path let a short or malformed reply leak the receive buffer and drain the Receive queue. First, the speculative peek p = xdr_inline_decode(xdr, 0); /* five p++ reads follow */ asks xdr_inline_decode() for zero bytes, which returns xdr->p without consulting xdr->end. The five subsequent __be32 reads can then walk up to 20 bytes past the wire payload into stale regbuf contents and misclassify the reply as a backchannel call. Second, after the post-peek p = xdr_inline_decode(xdr, 3 * sizeof(*p)); if (unlikely(!p)) return true; the short-header arm returns true without calling rpcrdma_bc_receive_call(). The contract with the caller is that a true return transfers ownership of rep to the backchannel path: rpcrdma_reply_handler() if (rpcrdma_is_bcall(r_xprt, rep)) return; /* bare return, skips out_post */ ... out_post: rpcrdma_post_recvs(r_xprt, credits + ...); Because rpcrdma_bc_receive_call() never ran, no one took rep, but rpcrdma_reply_handler still bare-returns past rpcrdma_rep_put() and rpcrdma_post_recvs(). The rep, with its persistently DMA-mapped receive buffer, is orphaned on rb_all_reps and freed only at transport teardown. This completion reposts nothing, so its slot is reclaimed only when a later forward-channel reply reaches out_post and rpcrdma_post_recvs() allocates a fresh rep to backfill; absent that traffic the Receive queue drains and the peer's Sends draw RNR NAKs. Fix by consulting xdr->end after the zero-length peek so the five __be32 reads cannot run unless 20 bytes of wire payload remain. A byte-precise comparison against xdr->end is required because a non-4-aligned receive rounds the stream's word count up past the true payload. Also return false from the short-header arm so the reply falls through the normal out_norqst cleanup chain (rpcrdma_rep_put() plus rpcrdma_post_recvs()).

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: xprtrdma: Fix bcall rep leak and unbounded peek rpcrdma_is_bcall() decodes a reply's first words to decide whether the frame is a backchannel call. Two issues in that decode path let a short or malformed reply leak the receive buffer and drain the Receive queue. First, the speculative peek p = xdr_inline_decode(xdr, 0); /* five p++ reads follow */ asks xdr_inline_decode() for zero bytes, which returns xdr->p without consulting xdr->end. The five subsequent __be32 reads can then walk up to 20 bytes past the wire payload into stale regbuf contents and misclassify the reply as a backchannel call. Second, after the post-peek p = xdr_inline_decode(xdr, 3 * sizeof(*p)); if (unlikely(!p)) return true; the short-header arm returns true without calling rpcrdma_bc_receive_call(). The contract with the caller is that a true return transfers ownership of rep to the backchannel path: rpcrdma_reply_handler() if (rpcrdma_is_bcall(r_xprt, rep)) return; /* bare return, skips out_post */ ... out_post: rpcrdma_post_recvs(r_xprt, credits + ...); Because rpcrdma_bc_receive_call() never ran, no one took rep, but rpcrdma_reply_handler still bare-returns past rpcrdma_rep_put() and rpcrdma_post_recvs(). The rep, with its persistently DMA-mapped receive buffer, is orphaned on rb_all_reps and freed only at transport teardown. This completion reposts nothing, so its slot is reclaimed only when a later forward-channel reply reaches out_post and rpcrdma_post_recvs() allocates a fresh rep to backfill; absent that traffic the Receive queue drains and the peer's Sends draw RNR NAKs. Fix by consulting xdr->end after the zero-length peek so the five __be32 reads cannot run unless 20 bytes of wire payload remain. A byte-precise comparison against xdr->end is required because a non-4-aligned receive rounds the stream's word count up past the true payload. Also return false from the short-header arm so the reply falls through the normal out_norqst cleanup chain (rpcrdma_rep_put() plus rpcrdma_post_recvs()).

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.

BSI · German · WID-SEC-2026-2852Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260819Security Bulletin 19 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Aug 2026, published on 19 August 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-72399 Référence CVE CVE-2026-72412 https://www.cve.org/CVERecord?id=CVE-2026-72412 Référence CVE CVE-2026-72417 https://www.cve.org/CVERecord?id=CVE-2026-72417 Référence CVE CVE-2026-72422 https://www.cve.org/CVERecord?id=CVE-2026-72422 Référence CVE CVE-2026-72429 https://www.cve.org/CVERecord?id=CVE-2026-72429 Référence CVE CVE-2026-72436 https://www.cve.org/CVERecord?id=CVE-2026-72436 Référence CVE CVE-2026-72442 https://www.cve.org/CVERecord?id=CVE-2026-72442 Référence CVE CVE-2026-72451 https://www.cve.org/CVERecord?id=CVE-2026-72451 Référence CVE CVE-2026-72463 https://www.cve.org/CVERecord?id=CVE-2026-72463 Référence CVE CVE-2026-72466 https://www.cve.org/CVERecord?id=CVE-2026-72466 Référence CVE CVE-2026-72472 https://www.cve.org/CVERecord?id=CVE-2026-72472 Référence CVE CVE-2026-72473 https://www.cve.org/CVERecord?id=CVE-2026-72473 Référence CVE CVE-2026-72477 https://www.cve.org/CVERecord?id=CVE-2026-72477 Référence CVE CVE-2026-72491 https://www.cve.org/CVERecord?id=CVE-2026-72491 Référence CVE CVE-2026-72493 https://www.cve.org/CVERecord?id=CVE-2026-72493 Référence CVE CVE-2026-72494 https://www.cve.org/CVERecord?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72496 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-72437 Référence CVE CVE-2026-72438 https://www.cve.org/CVERecord?id=CVE-2026-72438 Référence CVE CVE-2026-72439 https://www.cve.org/CVERecord?id=CVE-2026-72439 Référence CVE CVE-2026-72440 https://www.cve.org/CVERecord?id=CVE-2026-72440 Référence CVE CVE-2026-72448 https://www.cve.org/CVERecord?id=CVE-2026-72448 Référence CVE CVE-2026-72450 https://www.cve.org/CVERecord?id=CVE-2026-72450 Référence CVE CVE-2026-72459 https://www.cve.org/CVERecord?id=CVE-2026-72459 Référence CVE CVE-2026-72460 https://www.cve.org/CVERecord?id=CVE-2026-72460 Référence CVE CVE-2026-72464 https://www.cve.org/CVERecord?id=CVE-2026-72464 Référence CVE CVE-2026-72466 https://www.cve.org/CVERecord?id=CVE-2026-72466 Référence CVE CVE-2026-72467 https://www.cve.org/CVERecord?id=CVE-2026-72467 Référence CVE CVE-2026-72468 https://www.cve.org/CVERecord?id=CVE-2026-72468 Référence CVE CVE-2026-72469 https://www.cve.org/CVERecord?id=CVE-2026-72469 Référence CVE CVE-2026-72473 https://www.cve.org/CVERecord?id=CVE-2026-72473 Référence CVE CVE-2026-72485 https://www.cve.org/CVERecord?id=CVE-2026-72485 Référence CVE CVE-2026-72487 https://www.cve.org/CVERecord?id=CVE-2026-72487 Référence CVE CVE-2026-72488 https://www.cve.org/CVERecord?id=CVE-2026-72488 Référence CVE CVE-2026-72494 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-72288 Référence CVE CVE-2026-72289 https://www.cve.org/CVERecord?id=CVE-2026-72289 Référence CVE CVE-2026-72296 https://www.cve.org/CVERecord?id=CVE-2026-72296 Référence CVE CVE-2026-72297 https://www.cve.org/CVERecord?id=CVE-2026-72297 Référence CVE CVE-2026-72323 https://www.cve.org/CVERecord?id=CVE-2026-72323 Référence CVE CVE-2026-72339 https://www.cve.org/CVERecord?id=CVE-2026-72339 Référence CVE CVE-2026-72389 https://www.cve.org/CVERecord?id=CVE-2026-72389 Référence CVE CVE-2026-72421 https://www.cve.org/CVERecord?id=CVE-2026-72421 Référence CVE CVE-2026-72450 https://www.cve.org/CVERecord?id=CVE-2026-72450 Référence CVE CVE-2026-72466 https://www.cve.org/CVERecord?id=CVE-2026-72466 Référence CVE CVE-2026-72487 https://www.cve.org/CVERecord?id=CVE-2026-72487 Référence CVE CVE-2026-72502 https://www.cve.org/CVERecord?id=CVE-2026-72502 Référence CVE CVE-2026-74255 https://www.cve.org/CVERecord?id=CVE-2026-74255 Référence CVE CVE-2026-74261 https://www.cve.org/CVERecord?id=CVE-2026-74261 Référence CVE CVE-2026-74265 https://www.cve.org/CVERecord?id=CVE-2026-74265 Référence CVE CVE-2026-74271 https://www.cve.org/CVERecord?id=CVE-2026-74271 Référence CVE CVE-2026-74278 https://www.cve.org/CVERecord?id=CVE-2026-74278 Référence CVE CVE-2026-74279 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-72399 Référence CVE CVE-2026-72412 https://www.cve.org/CVERecord?id=CVE-2026-72412 Référence CVE CVE-2026-72417 https://www.cve.org/CVERecord?id=CVE-2026-72417 Référence CVE CVE-2026-72422 https://www.cve.org/CVERecord?id=CVE-2026-72422 Référence CVE CVE-2026-72429 https://www.cve.org/CVERecord?id=CVE-2026-72429 Référence CVE CVE-2026-72436 https://www.cve.org/CVERecord?id=CVE-2026-72436 Référence CVE CVE-2026-72442 https://www.cve.org/CVERecord?id=CVE-2026-72442 Référence CVE CVE-2026-72451 https://www.cve.org/CVERecord?id=CVE-2026-72451 Référence CVE CVE-2026-72463 https://www.cve.org/CVERecord?id=CVE-2026-72463 Référence CVE CVE-2026-72466 https://www.cve.org/CVERecord?id=CVE-2026-72466 Référence CVE CVE-2026-72472 https://www.cve.org/CVERecord?id=CVE-2026-72472 Référence CVE CVE-2026-72473 https://www.cve.org/CVERecord?id=CVE-2026-72473 Référence CVE CVE-2026-72477 https://www.cve.org/CVERecord?id=CVE-2026-72477 Référence CVE CVE-2026-72491 https://www.cve.org/CVERecord?id=CVE-2026-72491 Référence CVE CVE-2026-72493 https://www.cve.org/CVERecord?id=CVE-2026-72493 Référence CVE CVE-2026-72494 https://www.cve.org/CVERecord?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72496 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-72307 Référence CVE CVE-2026-72308 https://www.cve.org/CVERecord?id=CVE-2026-72308 Référence CVE CVE-2026-72317 https://www.cve.org/CVERecord?id=CVE-2026-72317 Référence CVE CVE-2026-72341 https://www.cve.org/CVERecord?id=CVE-2026-72341 Référence CVE CVE-2026-72342 https://www.cve.org/CVERecord?id=CVE-2026-72342 Référence CVE CVE-2026-72343 https://www.cve.org/CVERecord?id=CVE-2026-72343 Référence CVE CVE-2026-72389 https://www.cve.org/CVERecord?id=CVE-2026-72389 Référence CVE CVE-2026-72463 https://www.cve.org/CVERecord?id=CVE-2026-72463 Référence CVE CVE-2026-72464 https://www.cve.org/CVERecord?id=CVE-2026-72464 Référence CVE CVE-2026-72466 https://www.cve.org/CVERecord?id=CVE-2026-72466 Référence CVE CVE-2026-72467 https://www.cve.org/CVERecord?id=CVE-2026-72467 Référence CVE CVE-2026-72469 https://www.cve.org/CVERecord?id=CVE-2026-72469 Référence CVE CVE-2026-72473 https://www.cve.org/CVERecord?id=CVE-2026-72473 Référence CVE CVE-2026-72494 https://www.cve.org/CVERecord?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72496 https://www.cve.org/CVERecord?id=CVE-2026-72496 Référence CVE CVE-2026-72497 https://www.cve.org/CVERecord?id=CVE-2026-72497 Référence CVE CVE-2026-72498 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-72383 Référence CVE CVE-2026-72398 https://www.cve.org/CVERecord?id=CVE-2026-72398 Référence CVE CVE-2026-72399 https://www.cve.org/CVERecord?id=CVE-2026-72399 Référence CVE CVE-2026-72421 https://www.cve.org/CVERecord?id=CVE-2026-72421 Référence CVE CVE-2026-72422 https://www.cve.org/CVERecord?id=CVE-2026-72422 Référence CVE CVE-2026-72434 https://www.cve.org/CVERecord?id=CVE-2026-72434 Référence CVE CVE-2026-72436 https://www.cve.org/CVERecord?id=CVE-2026-72436 Référence CVE CVE-2026-72451 https://www.cve.org/CVERecord?id=CVE-2026-72451 Référence CVE CVE-2026-72454 https://www.cve.org/CVERecord?id=CVE-2026-72454 Référence CVE CVE-2026-72466 https://www.cve.org/CVERecord?id=CVE-2026-72466 Référence CVE CVE-2026-72472 https://www.cve.org/CVERecord?id=CVE-2026-72472 Référence CVE CVE-2026-72473 https://www.cve.org/CVERecord?id=CVE-2026-72473 Référence CVE CVE-2026-72487 https://www.cve.org/CVERecord?id=CVE-2026-72487 Référence CVE CVE-2026-72488 https://www.cve.org/CVERecord?id=CVE-2026-72488 Référence CVE CVE-2026-72489 https://www.cve.org/CVERecord?id=CVE-2026-72489 Référence CVE CVE-2026-72491 https://www.cve.org/CVERecord?id=CVE-2026-72491 Référence CVE CVE-2026-72494 https://www.cve.org/CVERecord?id=CVE-2026-72494 Référence CVE CVE-2026-72495 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-72307 Référence CVE CVE-2026-72308 https://www.cve.org/CVERecord?id=CVE-2026-72308 Référence CVE CVE-2026-72317 https://www.cve.org/CVERecord?id=CVE-2026-72317 Référence CVE CVE-2026-72341 https://www.cve.org/CVERecord?id=CVE-2026-72341 Référence CVE CVE-2026-72342 https://www.cve.org/CVERecord?id=CVE-2026-72342 Référence CVE CVE-2026-72343 https://www.cve.org/CVERecord?id=CVE-2026-72343 Référence CVE CVE-2026-72389 https://www.cve.org/CVERecord?id=CVE-2026-72389 Référence CVE CVE-2026-72463 https://www.cve.org/CVERecord?id=CVE-2026-72463 Référence CVE CVE-2026-72464 https://www.cve.org/CVERecord?id=CVE-2026-72464 Référence CVE CVE-2026-72466 https://www.cve.org/CVERecord?id=CVE-2026-72466 Référence CVE CVE-2026-72467 https://www.cve.org/CVERecord?id=CVE-2026-72467 Référence CVE CVE-2026-72469 https://www.cve.org/CVERecord?id=CVE-2026-72469 Référence CVE CVE-2026-72473 https://www.cve.org/CVERecord?id=CVE-2026-72473 Référence CVE CVE-2026-72494 https://www.cve.org/CVERecord?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72496 https://www.cve.org/CVERecord?id=CVE-2026-72496 Référence CVE CVE-2026-72497 https://www.cve.org/CVERecord?id=CVE-2026-72497 Référence CVE CVE-2026-72498 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: < 4.14, 5.15.212 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.97 ≤ 6.12.*, 6.18.40 ≤ 6.18.*, 7.1.5 ≤ 7.1.*, 7.2 ≤ *
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 15 Aug 2026 · Last source change 17 Aug 2026, 05:44 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-23
European sourceENISA EUVD · EUVD-2026-59365
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
    41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 0cee8f9c3b14bd6dee9c4310090a7f45b89b834f; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 7afc2f8d2fd9394724df9eaf22ce7a71029a5fba; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 88b5346284a184a6b7d019912232a571d672d3e3; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 07aa506436be7634e381e1e1f6d0efa9efc81ecc; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < d7a2870dde3bb09d51d6b9c877642996ad6b92dd; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 118a16a18c59f7ad8084b2d13988839b669fca10; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < c7653d5cebc8492c77ec0415b5e9c0fb3e644bc6; 4.14 · Fixed: < 4.14; 5.15.212 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 0cee8f9c3b14bd6dee9c4310090a7f45b89b834f; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 7afc2f8d2fd9394724df9eaf22ce7a71029a5fba; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 88b5346284a184a6b7d019912232a571d672d3e3; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 07aa506436be7634e381e1e1f6d0efa9efc81ecc; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < d7a2870dde3bb09d51d6b9c877642996ad6b92dd; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < 118a16a18c59f7ad8084b2d13988839b669fca10; 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 < c7653d5cebc8492c77ec0415b5e9c0fb3e644bc6; 4.14 · Fixed: < 4.14; 5.15.212 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  2. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    CNA ↗
  3. CVSS scoreCVSS score changed from not recorded to 9.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    9.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
    CNA ↗
  4. Catalogue recordCVE added to the BlackTree catalogue.
    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-59365↗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-72466 · cve.blacktree.nl