BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-40155High confidence

iommu/vt-d: debugfs: Fix legacy mode page table dump logic

Linux · Linux

7.3HighCVSS 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 204 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 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% 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 204 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.57-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.6-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.

1 current
CVE-2025-40155 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: iommu/vt-d: debugfs: Fix legacy mode page table dump logic
184 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 IOMMU VT-d debugfs code: in legacy mode page-table dump logic, if the translation type (TT) is neither 00b nor 01b, the SSPTPTR value may be left uninitialized or zero. This can lead to a general protection fault (GPF) when debugfs walks page tables under these conditions.
Remediation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
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-2025-124928

No EUVD known-exploited evidence

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

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 204 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: iommu/vt-d: debugfs: Fix legacy mode page table dump logic In legacy mode, SSPTPTR is ignored if TT is not 00b or 01b. SSPTPTR maybe uninitialized or zero in that case and may cause oops like: Oops: general protection fault, probably for non-canonical address 0xf00087d3f000f000: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 786 Comm: cat Not tainted 6.16.0 #191 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014 RIP: 0010:pgtable_walk_level+0x98/0x150 RSP: 0018:ffffc90000f279c0 EFLAGS: 00010206 RAX: 0000000040000000 RBX: ffffc90000f27ab0 RCX: 000000000000001e RDX: 0000000000000003 RSI: f00087d3f000f000 RDI: f00087d3f0010000 RBP: ffffc90000f27a00 R08: ffffc90000f27a98 R09: 0000000000000002 R10: 0000000000000000 R11: 0000000000000000 R12: f00087d3f000f000 R13: 0000000000000000 R14: 0000000040000000 R15: ffffc90000f27a98 FS: 0000764566dcb740(0000) GS:ffff8881f812c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000764566d44000 CR3: 0000000109d81003 CR4: 0000000000772ef0 PKRU: 55555554 Call Trace: <TASK> pgtable_walk_level+0x88/0x150 domain_translation_struct_show.isra.0+0x2d9/0x300 dev_domain_translation_struct_show+0x20/0x40 seq_read_iter+0x12d/0x490 ... Avoid walking the page table if TT is not 00b or 01b.

What

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: debugfs: Fix legacy mode page table dump logic In legacy mode, SSPTPTR is ignored if TT is not 00b or 01b. SSPTPTR maybe uninitialized or zero in that case and may cause oops like: Oops: general protection fault, probably for non-canonical address 0xf00087d3f000f000: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 786 Comm: cat Not tainted 6.16.0 #191 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014 RIP: 0010:pgtable_walk_level+0x98/0x150 RSP: 0018:ffffc90000f279c0 EFLAGS: 00010206 RAX: 0000000040000000 RBX: ffffc90000f27ab0 RCX: 000000000000001e RDX: 0000000000000003 RSI: f00087d3f000f000 RDI: f00087d3f0010000 RBP: ffffc90000f27a00 R08: ffffc90000f27a98 R09: 0000000000000002 R10: 0000000000000000 R11: 0000000000000000 R12: f00087d3f000f000 R13: 0000000000000000 R14: 0000000040000000 R15: ffffc90000f27a98 FS: 0000764566dcb740(0000) GS:ffff8881f812c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000764566d44000 CR3: 0000000109d81003 CR4: 0000000000772ef0 PKRU: 55555554 Call Trace: <TASK> pgtable_walk_level+0x88/0x150 domain_translation_struct_show.isra.0+0x2d9/0x300 dev_domain_translation_struct_show+0x20/0x40 seq_read_iter+0x12d/0x490 ... Avoid walking the page table if TT is not 00b or 01b.

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: iommu/vt-d: debugfs: Fix legacy mode page table dump logic In legacy mode, SSPTPTR is ignored if TT is not 00b or 01b. SSPTPTR maybe uninitialized or zero in that case and may cause oops like: Oops: general protection fault, probably for non-canonical address 0xf00087d3f000f000: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 786 Comm: cat Not tainted 6.16.0 #191 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014 RIP: 0010:pgtable_walk_level+0x98/0x150 RSP: 0018:ffffc90000f279c0 EFLAGS: 00010206 RAX: 0000000040000000 RBX: ffffc90000f27ab0 RCX: 000000000000001e RDX: 0000000000000003 RSI: f00087d3f000f000 RDI: f00087d3f0010000 RBP: ffffc90000f27a00 R08: ffffc90000f27a98 R09: 0000000000000002 R10: 0000000000000000 R11: 0000000000000000 R12: f00087d3f000f000 R13: 0000000000000000 R14: 0000000040000000 R15: ffffc90000f27a98 FS: 0000764566dcb740(0000) GS:ffff8881f812c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000764566d44000 CR3: 0000000109d81003 CR4: 0000000000772ef0 PKRU: 55555554 Call Trace: <TASK> pgtable_walk_level+0x88/0x150 domain_translation_struct_show.isra.0+0x2d9/0x300 dev_domain_translation_struct_show+0x20/0x40 seq_read_iter+0x12d/0x490 ... Avoid walking the page table if TT is not 00b or 01b.

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
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.ILowIntegrity impact: A successful attack can cause a limited 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.

BSI · German · WID-SEC-2025-2579Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251119Security Bulletin 19 Nov 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Nov 2025, published on 19 November 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 https://www.cve.org/CVERecord?id=CVE-2025-40140 Référence CVE CVE-2025-40141 https://www.cve.org/CVERecord?id=CVE-2025-40141 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40155 https://www.cve.org/CVERecord?id=CVE-2025-40155 Référence CVE CVE-2025-40156 https://www.cve.org/CVERecord?id=CVE-2025-40156 Référence CVE CVE-2025-40159 https://www.cve.org/CVERecord?id=CVE-2025-40159 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=CVE-2025-40164 Référence CVE CVE-2025-40165 https://www.cve.org/CVERecord?id=CVE-2025-40165 Référence CVE CVE-2025-40166 https://www.cve.org/CVERecord?id=CVE-2025-40166 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40169 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 https://www.cve.org/CVERecord?id=CVE-2025-40140 Référence CVE CVE-2025-40141 https://www.cve.org/CVERecord?id=CVE-2025-40141 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40155 https://www.cve.org/CVERecord?id=CVE-2025-40155 Référence CVE CVE-2025-40156 https://www.cve.org/CVERecord?id=CVE-2025-40156 Référence CVE CVE-2025-40159 https://www.cve.org/CVERecord?id=CVE-2025-40159 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=CVE-2025-40164 Référence CVE CVE-2025-40165 https://www.cve.org/CVERecord?id=CVE-2025-40165 Référence CVE CVE-2025-40166 https://www.cve.org/CVERecord?id=CVE-2025-40166 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40169 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 https://www.cve.org/CVERecord?id=CVE-2025-40140 Référence CVE CVE-2025-40141 https://www.cve.org/CVERecord?id=CVE-2025-40141 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40155 https://www.cve.org/CVERecord?id=CVE-2025-40155 Référence CVE CVE-2025-40156 https://www.cve.org/CVERecord?id=CVE-2025-40156 Référence CVE CVE-2025-40159 https://www.cve.org/CVERecord?id=CVE-2025-40159 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40165 https://www.cve.org/CVERecord?id=CVE-2025-40165 Référence CVE CVE-2025-40166 https://www.cve.org/CVERecord?id=CVE-2025-40166 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40169 https://www.cve.org/CVERecord?id=CVE-2025-40169 Référence CVE CVE-2025-40171 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 https://www.cve.org/CVERecord?id=CVE-2025-40140 Référence CVE CVE-2025-40141 https://www.cve.org/CVERecord?id=CVE-2025-40141 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40155 https://www.cve.org/CVERecord?id=CVE-2025-40155 Référence CVE CVE-2025-40156 https://www.cve.org/CVERecord?id=CVE-2025-40156 Référence CVE CVE-2025-40159 https://www.cve.org/CVERecord?id=CVE-2025-40159 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40165 https://www.cve.org/CVERecord?id=CVE-2025-40165 Référence CVE CVE-2025-40166 https://www.cve.org/CVERecord?id=CVE-2025-40166 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40169 https://www.cve.org/CVERecord?id=CVE-2025-40169 Référence CVE CVE-2025-40171 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 https://www.cve.org/CVERecord?id=CVE-2025-40140 Référence CVE CVE-2025-40141 https://www.cve.org/CVERecord?id=CVE-2025-40141 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40155 https://www.cve.org/CVERecord?id=CVE-2025-40155 Référence CVE CVE-2025-40156 https://www.cve.org/CVERecord?id=CVE-2025-40156 Référence CVE CVE-2025-40159 https://www.cve.org/CVERecord?id=CVE-2025-40159 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40165 https://www.cve.org/CVERecord?id=CVE-2025-40165 Référence CVE CVE-2025-40166 https://www.cve.org/CVERecord?id=CVE-2025-40166 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40169 https://www.cve.org/CVERecord?id=CVE-2025-40169 Référence CVE CVE-2025-40171 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40145 Référence CVE CVE-2025-40146 https://www.cve.org/CVERecord?id=CVE-2025-40146 Référence CVE CVE-2025-40147 https://www.cve.org/CVERecord?id=CVE-2025-40147 Référence CVE CVE-2025-40148 https://www.cve.org/CVERecord?id=CVE-2025-40148 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40152 https://www.cve.org/CVERecord?id=CVE-2025-40152 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40155 https://www.cve.org/CVERecord?id=CVE-2025-40155 Référence CVE CVE-2025-40156 https://www.cve.org/CVERecord?id=CVE-2025-40156 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40159 https://www.cve.org/CVERecord?id=CVE-2025-40159 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40161 https://www.cve.org/CVERecord?id=CVE-2025-40161 Référence CVE CVE-2025-40162 https://www.cve.org/CVERecord?id=CVE-2025-40162 Référence CVE CVE-2025-40163 https://www.cve.org/CVERecord?id=CVE-2025-40163 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40146 Référence CVE CVE-2025-40147 https://www.cve.org/CVERecord?id=CVE-2025-40147 Référence CVE CVE-2025-40148 https://www.cve.org/CVERecord?id=CVE-2025-40148 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40151 https://www.cve.org/CVERecord?id=CVE-2025-40151 Référence CVE CVE-2025-40152 https://www.cve.org/CVERecord?id=CVE-2025-40152 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40155 https://www.cve.org/CVERecord?id=CVE-2025-40155 Référence CVE CVE-2025-40156 https://www.cve.org/CVERecord?id=CVE-2025-40156 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40159 https://www.cve.org/CVERecord?id=CVE-2025-40159 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40161 https://www.cve.org/CVERecord?id=CVE-2025-40161 Référence CVE CVE-2025-40162 https://www.cve.org/CVERecord?id=CVE-2025-40162 Référence CVE CVE-2025-40163 https://www.cve.org/CVERecord?id=CVE-2025-40163 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40145 Référence CVE CVE-2025-40146 https://www.cve.org/CVERecord?id=CVE-2025-40146 Référence CVE CVE-2025-40147 https://www.cve.org/CVERecord?id=CVE-2025-40147 Référence CVE CVE-2025-40148 https://www.cve.org/CVERecord?id=CVE-2025-40148 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40152 https://www.cve.org/CVERecord?id=CVE-2025-40152 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40155 https://www.cve.org/CVERecord?id=CVE-2025-40155 Référence CVE CVE-2025-40156 https://www.cve.org/CVERecord?id=CVE-2025-40156 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40159 https://www.cve.org/CVERecord?id=CVE-2025-40159 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40161 https://www.cve.org/CVERecord?id=CVE-2025-40161 Référence CVE CVE-2025-40162 https://www.cve.org/CVERecord?id=CVE-2025-40162 Référence CVE CVE-2025-40163 https://www.cve.org/CVERecord?id=CVE-2025-40163 Référence CVE CVE-2025-40164 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.7, 6.12.53 ≤ 6.12.*, 6.17.3 ≤ 6.17.*, 6.18 ≤ *
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
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
04

Evidence and provenance

Published 12 Nov 2025 · Last source change 5 Aug 2026, 12:08 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-124928
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD not scheduled

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 ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-2025-124928↗Vendor CSAF · Red Hat Product Security↗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-2025-40155 · cve.blacktree.nl