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

SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing

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 110 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.67% 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 110 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 · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian 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-72217 · CSAF 2.0 · revision 7 · interimSUSE Product Security TeamCVE-2026-72217
45 known affected

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

  • 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 Server 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server 16.0
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_28-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_29-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_31-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_32-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_33-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_34-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_35-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_36-default
Summary
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing xdr_buf_to_bvec() writes a bio_vec into the caller's array before testing whether that slot is in range, and the head branch performs the store with no check at all. When the caller's budget is exactly used up, the next store lands one element past the end of the array. The overflow label returns count - 1, which masks the surplus store but cannot undo it. rq_bvec, the array passed by nfsd_vfs_write(), is allocated to exactly rq_maxpages entries with no slack. The OOB store can land in adjacent slab memory; the bv_len and bv_offset fields written there are derived from client-supplied RPC payload sizes. Move the in-range check ahead of the store in the head, page-loop, and tail branches. With the check at the top of each sequence, count is incremented only after a successful store, so the overflow label can return count directly.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-72217 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing
76 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 SUNRPC component. The `xdr_buf_to_bvec()` function performs an out-of-bounds write when processing client-supplied RPC (Remote Procedure Call) payload sizes without proper boundary checks. A remote attacker could exploit this by crafting malicious RPC requests, leading to memory corruption. This could result in a denial of service or other system instability.
Remediation
Affected
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-58975

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 110 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: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing xdr_buf_to_bvec() writes a bio_vec into the caller's array before testing whether that slot is in range, and the head branch performs the store with no check at all. When the caller's budget is exactly used up, the next store lands one element past the end of the array. The overflow label returns count - 1, which masks the surplus store but cannot undo it. rq_bvec, the array passed by nfsd_vfs_write(), is allocated to exactly rq_maxpages entries with no slack. The OOB store can land in adjacent slab memory; the bv_len and bv_offset fields written there are derived from client-supplied RPC payload sizes. Move the in-range check ahead of the store in the head, page-loop, and tail branches. With the check at the top of each sequence, count is incremented only after a successful store, so the overflow label can return count directly.

What

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing xdr_buf_to_bvec() writes a bio_vec into the caller's array before testing whether that slot is in range, and the head branch performs the store with no check at all. When the caller's budget is exactly used up, the next store lands one element past the end of the array. The overflow label returns count - 1, which masks the surplus store but cannot undo it. rq_bvec, the array passed by nfsd_vfs_write(), is allocated to exactly rq_maxpages entries with no slack. The OOB store can land in adjacent slab memory; the bv_len and bv_offset fields written there are derived from client-supplied RPC payload sizes. Move the in-range check ahead of the store in the head, page-loop, and tail branches. With the check at the top of each sequence, count is incremented only after a successful store, so the overflow label can return count directly.

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: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing xdr_buf_to_bvec() writes a bio_vec into the caller's array before testing whether that slot is in range, and the head branch performs the store with no check at all. When the caller's budget is exactly used up, the next store lands one element past the end of the array. The overflow label returns count - 1, which masks the surplus store but cannot undo it. rq_bvec, the array passed by nfsd_vfs_write(), is allocated to exactly rq_maxpages entries with no slack. The OOB store can land in adjacent slab memory; the bv_len and bv_offset fields written there are derived from client-supplied RPC payload sizes. Move the in-range check ahead of the store in the head, page-loop, and tail branches. With the check at the top of each sequence, count is incremented only after a successful store, so the overflow label can return count directly.

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-72085 Référence CVE CVE-2026-72098 https://www.cve.org/CVERecord?id=CVE-2026-72098 Référence CVE CVE-2026-72129 https://www.cve.org/CVERecord?id=CVE-2026-72129 Référence CVE CVE-2026-72130 https://www.cve.org/CVERecord?id=CVE-2026-72130 Référence CVE CVE-2026-72137 https://www.cve.org/CVERecord?id=CVE-2026-72137 Référence CVE CVE-2026-72139 https://www.cve.org/CVERecord?id=CVE-2026-72139 Référence CVE CVE-2026-72191 https://www.cve.org/CVERecord?id=CVE-2026-72191 Référence CVE CVE-2026-72192 https://www.cve.org/CVERecord?id=CVE-2026-72192 Référence CVE CVE-2026-72194 https://www.cve.org/CVERecord?id=CVE-2026-72194 Référence CVE CVE-2026-72217 https://www.cve.org/CVERecord?id=CVE-2026-72217 Référence CVE CVE-2026-72220 https://www.cve.org/CVERecord?id=CVE-2026-72220 Référence CVE CVE-2026-72221 https://www.cve.org/CVERecord?id=CVE-2026-72221 Référence CVE CVE-2026-72222 https://www.cve.org/CVERecord?id=CVE-2026-72222 Référence CVE CVE-2026-72226 https://www.cve.org/CVERecord?id=CVE-2026-72226 Référence CVE CVE-2026-72234 https://www.cve.org/CVERecord?id=CVE-2026-72234 Référence CVE CVE-2026-72248 https://www.cve.org/CVERecord?id=CVE-2026-72248 Référence CVE CVE-2026-72249 https://www.cve.org/CVERecord?id=CVE-2026-72249 Référence CVE CVE-2026-72251 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-72108 Référence CVE CVE-2026-72132 https://www.cve.org/CVERecord?id=CVE-2026-72132 Référence CVE CVE-2026-72136 https://www.cve.org/CVERecord?id=CVE-2026-72136 Référence CVE CVE-2026-72137 https://www.cve.org/CVERecord?id=CVE-2026-72137 Référence CVE CVE-2026-72161 https://www.cve.org/CVERecord?id=CVE-2026-72161 Référence CVE CVE-2026-72163 https://www.cve.org/CVERecord?id=CVE-2026-72163 Référence CVE CVE-2026-72164 https://www.cve.org/CVERecord?id=CVE-2026-72164 Référence CVE CVE-2026-72176 https://www.cve.org/CVERecord?id=CVE-2026-72176 Référence CVE CVE-2026-72177 https://www.cve.org/CVERecord?id=CVE-2026-72177 Référence CVE CVE-2026-72217 https://www.cve.org/CVERecord?id=CVE-2026-72217 Référence CVE CVE-2026-72221 https://www.cve.org/CVERecord?id=CVE-2026-72221 Référence CVE CVE-2026-72222 https://www.cve.org/CVERecord?id=CVE-2026-72222 Référence CVE CVE-2026-72234 https://www.cve.org/CVERecord?id=CVE-2026-72234 Référence CVE CVE-2026-72242 https://www.cve.org/CVERecord?id=CVE-2026-72242 Référence CVE CVE-2026-72243 https://www.cve.org/CVERecord?id=CVE-2026-72243 Référence CVE CVE-2026-72251 https://www.cve.org/CVERecord?id=CVE-2026-72251 Référence CVE CVE-2026-72254 https://www.cve.org/CVERecord?id=CVE-2026-72254 Référence CVE CVE-2026-72280 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-72085 Référence CVE CVE-2026-72098 https://www.cve.org/CVERecord?id=CVE-2026-72098 Référence CVE CVE-2026-72129 https://www.cve.org/CVERecord?id=CVE-2026-72129 Référence CVE CVE-2026-72130 https://www.cve.org/CVERecord?id=CVE-2026-72130 Référence CVE CVE-2026-72137 https://www.cve.org/CVERecord?id=CVE-2026-72137 Référence CVE CVE-2026-72139 https://www.cve.org/CVERecord?id=CVE-2026-72139 Référence CVE CVE-2026-72191 https://www.cve.org/CVERecord?id=CVE-2026-72191 Référence CVE CVE-2026-72192 https://www.cve.org/CVERecord?id=CVE-2026-72192 Référence CVE CVE-2026-72194 https://www.cve.org/CVERecord?id=CVE-2026-72194 Référence CVE CVE-2026-72217 https://www.cve.org/CVERecord?id=CVE-2026-72217 Référence CVE CVE-2026-72220 https://www.cve.org/CVERecord?id=CVE-2026-72220 Référence CVE CVE-2026-72221 https://www.cve.org/CVERecord?id=CVE-2026-72221 Référence CVE CVE-2026-72222 https://www.cve.org/CVERecord?id=CVE-2026-72222 Référence CVE CVE-2026-72226 https://www.cve.org/CVERecord?id=CVE-2026-72226 Référence CVE CVE-2026-72234 https://www.cve.org/CVERecord?id=CVE-2026-72234 Référence CVE CVE-2026-72248 https://www.cve.org/CVERecord?id=CVE-2026-72248 Référence CVE CVE-2026-72249 https://www.cve.org/CVERecord?id=CVE-2026-72249 Référence CVE CVE-2026-72251 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-72124 Référence CVE CVE-2026-72125 https://www.cve.org/CVERecord?id=CVE-2026-72125 Référence CVE CVE-2026-72126 https://www.cve.org/CVERecord?id=CVE-2026-72126 Référence CVE CVE-2026-72129 https://www.cve.org/CVERecord?id=CVE-2026-72129 Référence CVE CVE-2026-72130 https://www.cve.org/CVERecord?id=CVE-2026-72130 Référence CVE CVE-2026-72191 https://www.cve.org/CVERecord?id=CVE-2026-72191 Référence CVE CVE-2026-72192 https://www.cve.org/CVERecord?id=CVE-2026-72192 Référence CVE CVE-2026-72194 https://www.cve.org/CVERecord?id=CVE-2026-72194 Référence CVE CVE-2026-72200 https://www.cve.org/CVERecord?id=CVE-2026-72200 Référence CVE CVE-2026-72217 https://www.cve.org/CVERecord?id=CVE-2026-72217 Référence CVE CVE-2026-72221 https://www.cve.org/CVERecord?id=CVE-2026-72221 Référence CVE CVE-2026-72222 https://www.cve.org/CVERecord?id=CVE-2026-72222 Référence CVE CVE-2026-72226 https://www.cve.org/CVERecord?id=CVE-2026-72226 Référence CVE CVE-2026-72234 https://www.cve.org/CVERecord?id=CVE-2026-72234 Référence CVE CVE-2026-72251 https://www.cve.org/CVERecord?id=CVE-2026-72251 Référence CVE CVE-2026-72255 https://www.cve.org/CVERecord?id=CVE-2026-72255 Référence CVE CVE-2026-72288 https://www.cve.org/CVERecord?id=CVE-2026-72288 Référence CVE CVE-2026-72289 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: < 6.6, 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:41 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-58975
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-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 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 16.0; kernel-devel as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-macros as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-source as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-source-vanilla as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-default as component of SUSE Linux Micro 6.2; kernel-devel as component of SUSE Linux Micro 6.2; kernel-macros as component of SUSE Linux Micro 6.2; kernel-source as component of SUSE Linux Micro 6.2; SUSE Linux Micro Extras 6.2:kernel-obs-build; SUSE Linux Micro Extras 6.2:kernel-syms; kernel-source as component of openSUSE Leap 16.0
    After
    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 Server 16.0; kernel-devel as component of SUSE Linux Enterprise Server 16.0; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_33-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_34-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_35-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_36-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_37-default; 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 16.0; kernel-devel as component of SUSE Linux Enterprise Server for SAP applications 16.0; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_33-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_34-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_35-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_36-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_37-default; kernel-macros as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-source as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-source-vanilla as component of SUSE Linux Enterprise Server for SAP applications 16.0; and 15 more
    SUSE Product Security Team ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    2eb2b93581813b74c7174961126f6ec38eadb5a7 < 4a1148f2739d5089c3ca8ae2e9d1053e219ab5df; 2eb2b93581813b74c7174961126f6ec38eadb5a7 < 6029e711a818bf34d6c4b90cafee24f3afffa110; 2eb2b93581813b74c7174961126f6ec38eadb5a7 < 69e18135e2a004a79505451dbef07314ea16e1eb; 2eb2b93581813b74c7174961126f6ec38eadb5a7 < 98414b42530af65cb984ffc12685096a3b5e179a; 2eb2b93581813b74c7174961126f6ec38eadb5a7 < 42f5b80dda6b86e424054baf1475df686c403d5c; 6.6 · Fixed: < 6.6; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    2eb2b93581813b74c7174961126f6ec38eadb5a7 < 4a1148f2739d5089c3ca8ae2e9d1053e219ab5df; 2eb2b93581813b74c7174961126f6ec38eadb5a7 < 6029e711a818bf34d6c4b90cafee24f3afffa110; 2eb2b93581813b74c7174961126f6ec38eadb5a7 < 69e18135e2a004a79505451dbef07314ea16e1eb; 2eb2b93581813b74c7174961126f6ec38eadb5a7 < 98414b42530af65cb984ffc12685096a3b5e179a; 2eb2b93581813b74c7174961126f6ec38eadb5a7 < 42f5b80dda6b86e424054baf1475df686c403d5c; 6.6 · Fixed: < 6.6; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  3. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    CNA ↗
  4. 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 ↗
  5. 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-58975↗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-72217 · cve.blacktree.nl