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

octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

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.101-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 5 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-72045 · CSAF 2.0 · revision 7 · interimSUSE Product Security TeamCVE-2026-72045
221 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: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF rvu_mbox_handler_lmtst_tbl_setup() uses req->base_pcifunc as a direct index into the LMT map table to read another function's LMTLINE physical base address and copy it into the caller's own LMT map table entry. The mailbox dispatcher authenticates req->hdr.pcifunc from the IRQ source, but req->base_pcifunc is a separate payload field and is not sanitized. Reject the request with -EPERM when a VF caller's base_pcifunc is not a valid function under its own PF. is_pf_func_valid() bounds the FUNC field to the PF's configured VF count, keeping the computed index inside the caller's own slot block.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-72045 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF
98 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 component `octeontx2-af`. A local attacker with access to a Virtual Function (VF) could exploit an unsanitized input in the `rvu_mbox_handler_lmtst_tbl_setup()` function. This vulnerability allows the VF to read the physical base address of another function's LMTLINE, which could lead to information disclosure and unauthorized access to sensitive system memory.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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-59003

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF rvu_mbox_handler_lmtst_tbl_setup() uses req->base_pcifunc as a direct index into the LMT map table to read another function's LMTLINE physical base address and copy it into the caller's own LMT map table entry. The mailbox dispatcher authenticates req->hdr.pcifunc from the IRQ source, but req->base_pcifunc is a separate payload field and is not sanitized. Reject the request with -EPERM when a VF caller's base_pcifunc is not a valid function under its own PF. is_pf_func_valid() bounds the FUNC field to the PF's configured VF count, keeping the computed index inside the caller's own slot block.

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF rvu_mbox_handler_lmtst_tbl_setup() uses req->base_pcifunc as a direct index into the LMT map table to read another function's LMTLINE physical base address and copy it into the caller's own LMT map table entry. The mailbox dispatcher authenticates req->hdr.pcifunc from the IRQ source, but req->base_pcifunc is a separate payload field and is not sanitized. Reject the request with -EPERM when a VF caller's base_pcifunc is not a valid function under its own PF. is_pf_func_valid() bounds the FUNC field to the PF's configured VF count, keeping the computed index inside the caller's own slot block.

What

In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF rvu_mbox_handler_lmtst_tbl_setup() uses req->base_pcifunc as a direct index into the LMT map table to read another function's LMTLINE physical base address and copy it into the caller's own LMT map table entry. The mailbox dispatcher authenticates req->hdr.pcifunc from the IRQ source, but req->base_pcifunc is a separate payload field and is not sanitized. Reject the request with -EPERM when a VF caller's base_pcifunc is not a valid function under its own PF. is_pf_func_valid() bounds the FUNC field to the PF's configured VF count, keeping the computed index inside the caller's own slot block.

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF rvu_mbox_handler_lmtst_tbl_setup() uses req->base_pcifunc as a direct index into the LMT map table to read another function's LMTLINE physical base address and copy it into the caller's own LMT map table entry. The mailbox dispatcher authenticates req->hdr.pcifunc from the IRQ source, but req->base_pcifunc is a separate payload field and is not sanitized. Reject the request with -EPERM when a VF caller's base_pcifunc is not a valid function under its own PF. is_pf_func_valid() bounds the FUNC field to the PF's configured VF count, keeping the computed index inside the caller's own slot block.

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different 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:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security 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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-59003Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF rvu_mbox_handler_lmtst_tbl_setup() uses req->base_pcifunc as a direct index into the LMT map table to read another function's LMTLINE physical base address and copy it into the caller's own LMT map table entry. The mailbox dispatcher authenticates req->hdr.pcifunc from the IRQ source, but req->base_pcifunc is a separate payload field and is not sanitized. Reject the request with -EPERM when a VF caller's base_pcifunc is not a valid function under its own PF. is_pf_func_valid() bounds the FUNC field to the PF's configured VF count, keeping the computed index inside the caller's own slot block.

Official EUVD record ↗
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-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-72017 Référence CVE CVE-2026-72019 https://www.cve.org/CVERecord?id=CVE-2026-72019 Référence CVE CVE-2026-72020 https://www.cve.org/CVERecord?id=CVE-2026-72020 Référence CVE CVE-2026-72022 https://www.cve.org/CVERecord?id=CVE-2026-72022 Référence CVE CVE-2026-72023 https://www.cve.org/CVERecord?id=CVE-2026-72023 Référence CVE CVE-2026-72032 https://www.cve.org/CVERecord?id=CVE-2026-72032 Référence CVE CVE-2026-72034 https://www.cve.org/CVERecord?id=CVE-2026-72034 Référence CVE CVE-2026-72035 https://www.cve.org/CVERecord?id=CVE-2026-72035 Référence CVE CVE-2026-72036 https://www.cve.org/CVERecord?id=CVE-2026-72036 Référence CVE CVE-2026-72045 https://www.cve.org/CVERecord?id=CVE-2026-72045 Référence CVE CVE-2026-72046 https://www.cve.org/CVERecord?id=CVE-2026-72046 Référence CVE CVE-2026-72051 https://www.cve.org/CVERecord?id=CVE-2026-72051 Référence CVE CVE-2026-72052 https://www.cve.org/CVERecord?id=CVE-2026-72052 Référence CVE CVE-2026-72053 https://www.cve.org/CVERecord?id=CVE-2026-72053 Référence CVE CVE-2026-72054 https://www.cve.org/CVERecord?id=CVE-2026-72054 Référence CVE CVE-2026-72055 https://www.cve.org/CVERecord?id=CVE-2026-72055 Référence CVE CVE-2026-72061 https://www.cve.org/CVERecord?id=CVE-2026-72061 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64456 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-68128 https://www.cve.org/CVERecord?id=CVE-2026-68128 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68200 https://www.cve.org/CVERecord?id=CVE-2026-68200 Référence CVE CVE-2026-68264 https://www.cve.org/CVERecord?id=CVE-2026-68264 Référence CVE CVE-2026-68294 https://www.cve.org/CVERecord?id=CVE-2026-68294 Référence CVE CVE-2026-68363 https://www.cve.org/CVERecord?id=CVE-2026-68363 Référence CVE CVE-2026-68426 https://www.cve.org/CVERecord?id=CVE-2026-68426 Référence CVE CVE-2026-72045 https://www.cve.org/CVERecord?id=CVE-2026-72045 Référence CVE CVE-2026-72098 https://www.cve.org/CVERecord?id=CVE-2026-72098 Référence CVE CVE-2026-72102 https://www.cve.org/CVERecord?id=CVE-2026-72102 Référence CVE CVE-2026-72298 https://www.cve.org/CVERecord?id=CVE-2026-72298 Référence CVE CVE-2026-74480 https://www.cve.org/CVERecord?id=CVE-2026-74480 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Gestion détaillée du document le 18 septembre 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.g

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

d?id=CVE-2026-68480 Référence CVE CVE-2026-72012 https://www.cve.org/CVERecord?id=CVE-2026-72012 Référence CVE CVE-2026-72015 https://www.cve.org/CVERecord?id=CVE-2026-72015 Référence CVE CVE-2026-72017 https://www.cve.org/CVERecord?id=CVE-2026-72017 Référence CVE CVE-2026-72023 https://www.cve.org/CVERecord?id=CVE-2026-72023 Référence CVE CVE-2026-72030 https://www.cve.org/CVERecord?id=CVE-2026-72030 Référence CVE CVE-2026-72035 https://www.cve.org/CVERecord?id=CVE-2026-72035 Référence CVE CVE-2026-72040 https://www.cve.org/CVERecord?id=CVE-2026-72040 Référence CVE CVE-2026-72041 https://www.cve.org/CVERecord?id=CVE-2026-72041 Référence CVE CVE-2026-72045 https://www.cve.org/CVERecord?id=CVE-2026-72045 Référence CVE CVE-2026-72051 https://www.cve.org/CVERecord?id=CVE-2026-72051 Référence CVE CVE-2026-72057 https://www.cve.org/CVERecord?id=CVE-2026-72057 Référence CVE CVE-2026-72062 https://www.cve.org/CVERecord?id=CVE-2026-72062 Référence CVE CVE-2026-72063 https://www.cve.org/CVERecord?id=CVE-2026-72063 Référence CVE CVE-2026-72065 https://www.cve.org/CVERecord?id=CVE-2026-72065 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72070 https://www.cve.org/CVERecord?id=CVE-2026-72070 Référence CVE CVE-2026-72077 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68446 Référence CVE CVE-2026-68449 https://www.cve.org/CVERecord?id=CVE-2026-68449 Référence CVE CVE-2026-68450 https://www.cve.org/CVERecord?id=CVE-2026-68450 Référence CVE CVE-2026-72015 https://www.cve.org/CVERecord?id=CVE-2026-72015 Référence CVE CVE-2026-72017 https://www.cve.org/CVERecord?id=CVE-2026-72017 Référence CVE CVE-2026-72023 https://www.cve.org/CVERecord?id=CVE-2026-72023 Référence CVE CVE-2026-72030 https://www.cve.org/CVERecord?id=CVE-2026-72030 Référence CVE CVE-2026-72032 https://www.cve.org/CVERecord?id=CVE-2026-72032 Référence CVE CVE-2026-72040 https://www.cve.org/CVERecord?id=CVE-2026-72040 Référence CVE CVE-2026-72045 https://www.cve.org/CVERecord?id=CVE-2026-72045 Référence CVE CVE-2026-72046 https://www.cve.org/CVERecord?id=CVE-2026-72046 Référence CVE CVE-2026-72051 https://www.cve.org/CVERecord?id=CVE-2026-72051 Référence CVE CVE-2026-72062 https://www.cve.org/CVERecord?id=CVE-2026-72062 Référence CVE CVE-2026-72065 https://www.cve.org/CVERecord?id=CVE-2026-72065 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72070 https://www.cve.org/CVERecord?id=CVE-2026-72070 Référence CVE CVE-2026-72101 https://www.cve.org/CVERecord?id=CVE-2026-72101 Référence CVE CVE-2026-72103 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.14, 5.15.217 ≤ 5.15.*, 6.1.184 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 15 Aug 2026 · Last source change 23 Aug 2026, 12:46 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-59003
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. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-72045 to remediation: access.redhat.com/CVE-2026-72045.
    Before
    remediation: access.redhat.com/CVE-2026-72045
    After
    remediation: access.redhat.com/CVE-2026-72045
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. 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 154 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 68 more · Fixed: kernel-64k-debug-debuginfo-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-matched-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debuginfo-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-matched-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.48.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.48.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.48.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.48.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.48.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.48.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.48.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.48.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.48.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.48.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.48.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.48.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-aarch64-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-ppc64le-0:5.14.0-687.48.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-s390x-0:5.14.0-687.48.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-x86_64-0:5.14.0-687.48.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.48.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.48.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.48.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.48.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); and 273 more
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/04c014e49b9f53d58a8f94adece8a0af3ae1b85c; removed remediation: git.kernel.org/e9c5b03208507dd6d58b0c23a2c60b5c2f4c1b11.
    Before
    remediation: git.kernel.org/e9c5b03208507dd6d58b0c23a2c60b5c2f4c1b11
    After
    remediation: git.kernel.org/04c014e49b9f53d58a8f94adece8a0af3ae1b85c
    CNA ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    893ae97214c385be02f8ec097298cc48c7f0d905 < e9c5b03208507dd6d58b0c23a2c60b5c2f4c1b11; 893ae97214c385be02f8ec097298cc48c7f0d905 < 54535692bec9ef464adc714108eb19e49e38b5a2; 893ae97214c385be02f8ec097298cc48c7f0d905 < c73b8795b45f4ad5a95120d2e9b435ea4616e08e; 893ae97214c385be02f8ec097298cc48c7f0d905 < 59da37fee81a8d76079313348ca13c5bc90dd6ae; 893ae97214c385be02f8ec097298cc48c7f0d905 < 8cdcf3d2caacdee7ddd363705fb4d93b0c1a0915; 5.14 · Fixed: < 5.14; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    After
    893ae97214c385be02f8ec097298cc48c7f0d905 < 04c014e49b9f53d58a8f94adece8a0af3ae1b85c; 893ae97214c385be02f8ec097298cc48c7f0d905 < 6967dd944be2a71eddab3a2ae1a1a4dd9e5f8eed; 893ae97214c385be02f8ec097298cc48c7f0d905 < e9c5b03208507dd6d58b0c23a2c60b5c2f4c1b11; 893ae97214c385be02f8ec097298cc48c7f0d905 < 54535692bec9ef464adc714108eb19e49e38b5a2; 893ae97214c385be02f8ec097298cc48c7f0d905 < c73b8795b45f4ad5a95120d2e9b435ea4616e08e; 893ae97214c385be02f8ec097298cc48c7f0d905 < 59da37fee81a8d76079313348ca13c5bc90dd6ae; 893ae97214c385be02f8ec097298cc48c7f0d905 < 8cdcf3d2caacdee7ddd363705fb4d93b0c1a0915; 5.14 · Fixed: < 5.14; 5.15.217 ≤ 5.15.*; 6.1.184 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    893ae97214c385be02f8ec097298cc48c7f0d905 < e9c5b03208507dd6d58b0c23a2c60b5c2f4c1b11; 893ae97214c385be02f8ec097298cc48c7f0d905 < 54535692bec9ef464adc714108eb19e49e38b5a2; 893ae97214c385be02f8ec097298cc48c7f0d905 < c73b8795b45f4ad5a95120d2e9b435ea4616e08e; 893ae97214c385be02f8ec097298cc48c7f0d905 < 59da37fee81a8d76079313348ca13c5bc90dd6ae; 893ae97214c385be02f8ec097298cc48c7f0d905 < 8cdcf3d2caacdee7ddd363705fb4d93b0c1a0915; 5.14 · Fixed: < 5.14; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    893ae97214c385be02f8ec097298cc48c7f0d905 < e9c5b03208507dd6d58b0c23a2c60b5c2f4c1b11; 893ae97214c385be02f8ec097298cc48c7f0d905 < 54535692bec9ef464adc714108eb19e49e38b5a2; 893ae97214c385be02f8ec097298cc48c7f0d905 < c73b8795b45f4ad5a95120d2e9b435ea4616e08e; 893ae97214c385be02f8ec097298cc48c7f0d905 < 59da37fee81a8d76079313348ca13c5bc90dd6ae; 893ae97214c385be02f8ec097298cc48c7f0d905 < 8cdcf3d2caacdee7ddd363705fb4d93b0c1a0915; 5.14 · Fixed: < 5.14; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  7. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  8. CVSS scoreCVSS score changed from not recorded to 8.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).
    Before
    not recorded
    After
    8.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H)
    CNA ↗
  9. 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-59003↗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-72045 · cve.blacktree.nl