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

ext4: guard against EA inode refcount underflow in xattr update

Linux · Linux

7.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 266 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • 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: Within 30 daysRemediation target: Within 180 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 266 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 · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.158-1Debian 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-40190 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ext4: guard against EA inode refcount underflow in xattr update
246 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 ext4 filesystem implementation in the Linux kernel. The function ext4_xattr_inode_update_ref() may read an EA-inode reference count that is already non-positive and then apply a negative change (-1), causing the reference count to underflow and the filesystem to treat the inode as corrupted. This may lead to unexpected filesystem errors or denial of service (e.g., the filesystem remounting read-only).
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-150384

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 266 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: ext4: guard against EA inode refcount underflow in xattr update syzkaller found a path where ext4_xattr_inode_update_ref() reads an EA inode refcount that is already <= 0 and then applies ref_change (often -1). That lets the refcount underflow and we proceed with a bogus value, triggering errors like: EXT4-fs error: EA inode <n> ref underflow: ref_count=-1 ref_change=-1 EXT4-fs warning: ea_inode dec ref err=-117 Make the invariant explicit: if the current refcount is non-positive, treat this as on-disk corruption, emit ext4_error_inode(), and fail the operation with -EFSCORRUPTED instead of updating the refcount. Delete the WARN_ONCE() as negative refcounts are now impossible; keep error reporting in ext4_error_inode(). This prevents the underflow and the follow-on orphan/cleanup churn.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: guard against EA inode refcount underflow in xattr update syzkaller found a path where ext4_xattr_inode_update_ref() reads an EA inode refcount that is already <= 0 and then applies ref_change (often -1). That lets the refcount underflow and we proceed with a bogus value, triggering errors like: EXT4-fs error: EA inode <n> ref underflow: ref_count=-1 ref_change=-1 EXT4-fs warning: ea_inode dec ref err=-117 Make the invariant explicit: if the current refcount is non-positive, treat this as on-disk corruption, emit ext4_error_inode(), and fail the operation with -EFSCORRUPTED instead of updating the refcount. Delete the WARN_ONCE() as negative refcounts are now impossible; keep error reporting in ext4_error_inode(). This prevents the underflow and the follow-on orphan/cleanup churn.

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 without authentication after a 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: ext4: guard against EA inode refcount underflow in xattr update syzkaller found a path where ext4_xattr_inode_update_ref() reads an EA inode refcount that is already <= 0 and then applies ref_change (often -1). That lets the refcount underflow and we proceed with a bogus value, triggering errors like: EXT4-fs error: EA inode <n> ref underflow: ref_count=-1 ref_change=-1 EXT4-fs warning: ea_inode dec ref err=-117 Make the invariant explicit: if the current refcount is non-positive, treat this as on-disk corruption, emit ext4_error_inode(), and fail the operation with -EFSCORRUPTED instead of updating the refcount. Delete the WARN_ONCE() as negative refcounts are now impossible; keep error reporting in ext4_error_inode(). This prevents the underflow and the follow-on orphan/cleanup churn.

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 without authentication after a 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
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
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:N/UI:R/S:U/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.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Unauthenticated
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-2595Linux 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-0369Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-40135 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=CVE-2025-40170 Référence CVE CVE-2025-40178 https://www.cve.org/CVERecord?id=CVE-2025-40178 Référence CVE CVE-2025-40179 https://www.cve.org/CVERecord?id=CVE-2025-40179 Référence CVE CVE-2025-40187 https://www.cve.org/CVERecord?id=CVE-2025-40187 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40192 https://www.cve.org/CVERecord?id=CVE-2025-40192 Référence CVE CVE-2025-40201 https://www.cve.org/CVERecord?id=CVE-2025-40201 Référence CVE CVE-2025-40202 https://www.cve.org/CVERecord?id=CVE-2025-40202 Référence CVE CVE-2025-40211 https://www.cve.org/CVERecord?id=CVE-2025-40211 Référence CVE CVE-2025-40215 https://www.cve.org/CVERecord?id=CVE-2025-40215 Référence CVE CVE-2025-40219 https://www.cve.org/CVERecord?id=CVE-2025-40219 Référence CVE CVE-2025-40220 https://www.cve.org/CVERecord?id=CVE-2025-40220 Référence CVE CVE-2025-40223 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-40139 Référence CVE CVE-2025-40146 https://www.cve.org/CVERecord?id=CVE-2025-40146 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 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-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=CVE-2025-40170 Référence CVE CVE-2025-40180 https://www.cve.org/CVERecord?id=CVE-2025-40180 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40192 https://www.cve.org/CVERecord?id=CVE-2025-40192 Référence CVE CVE-2025-40193 https://www.cve.org/CVERecord?id=CVE-2025-40193 Référence CVE CVE-2025-40195 https://www.cve.org/CVERecord?id=CVE-2025-40195 Référence CVE CVE-2025-40196 https://www.cve.org/CVERecord?id=CVE-2025-40196 Référence CVE CVE-2025-40198 https://www.cve.org/CVERecord?id=CVE-2025-40198 Référence CVE CVE-2025-40206 https://www.cve.org/CVERecord?id=CVE-2025-40206 Référence CVE CVE-2025-40208 https://www.cve.org/CVERecord?id=CVE-2025-40208 Référence CVE CVE-2025-40210 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-40139 Référence CVE CVE-2025-40146 https://www.cve.org/CVERecord?id=CVE-2025-40146 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 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-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=CVE-2025-40170 Référence CVE CVE-2025-40180 https://www.cve.org/CVERecord?id=CVE-2025-40180 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40192 https://www.cve.org/CVERecord?id=CVE-2025-40192 Référence CVE CVE-2025-40193 https://www.cve.org/CVERecord?id=CVE-2025-40193 Référence CVE CVE-2025-40195 https://www.cve.org/CVERecord?id=CVE-2025-40195 Référence CVE CVE-2025-40196 https://www.cve.org/CVERecord?id=CVE-2025-40196 Référence CVE CVE-2025-40198 https://www.cve.org/CVERecord?id=CVE-2025-40198 Référence CVE CVE-2025-40206 https://www.cve.org/CVERecord?id=CVE-2025-40206 Référence CVE CVE-2025-40208 https://www.cve.org/CVERecord?id=CVE-2025-40208 Référence CVE CVE-2025-40210 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40173 Référence CVE CVE-2025-40176 https://www.cve.org/CVERecord?id=CVE-2025-40176 Référence CVE CVE-2025-40178 https://www.cve.org/CVERecord?id=CVE-2025-40178 Référence CVE CVE-2025-40179 https://www.cve.org/CVERecord?id=CVE-2025-40179 Référence CVE CVE-2025-40180 https://www.cve.org/CVERecord?id=CVE-2025-40180 Référence CVE CVE-2025-40183 https://www.cve.org/CVERecord?id=CVE-2025-40183 Référence CVE CVE-2025-40186 https://www.cve.org/CVERecord?id=CVE-2025-40186 Référence CVE CVE-2025-40187 https://www.cve.org/CVERecord?id=CVE-2025-40187 Référence CVE CVE-2025-40188 https://www.cve.org/CVERecord?id=CVE-2025-40188 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40194 https://www.cve.org/CVERecord?id=CVE-2025-40194 Référence CVE CVE-2025-40195 https://www.cve.org/CVERecord?id=CVE-2025-40195 Référence CVE CVE-2025-40198 https://www.cve.org/CVERecord?id=CVE-2025-40198 Référence CVE CVE-2025-40200 https://www.cve.org/CVERecord?id=CVE-2025-40200 Référence CVE CVE-2025-40202 https://www.cve.org/CVERecord?id=CVE-2025-40202 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=CVE-2025-40204 Référence CVE CVE-2025-40205 https://www.cve.org/CVERecord?id=CVE-2025-40205 Référence CVE CVE-2025-40206 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40177 Référence CVE CVE-2025-40178 https://www.cve.org/CVERecord?id=CVE-2025-40178 Référence CVE CVE-2025-40179 https://www.cve.org/CVERecord?id=CVE-2025-40179 Référence CVE CVE-2025-40180 https://www.cve.org/CVERecord?id=CVE-2025-40180 Référence CVE CVE-2025-40181 https://www.cve.org/CVERecord?id=CVE-2025-40181 Référence CVE CVE-2025-40183 https://www.cve.org/CVERecord?id=CVE-2025-40183 Référence CVE CVE-2025-40186 https://www.cve.org/CVERecord?id=CVE-2025-40186 Référence CVE CVE-2025-40187 https://www.cve.org/CVERecord?id=CVE-2025-40187 Référence CVE CVE-2025-40188 https://www.cve.org/CVERecord?id=CVE-2025-40188 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40194 https://www.cve.org/CVERecord?id=CVE-2025-40194 Référence CVE CVE-2025-40198 https://www.cve.org/CVERecord?id=CVE-2025-40198 Référence CVE CVE-2025-40200 https://www.cve.org/CVERecord?id=CVE-2025-40200 Référence CVE CVE-2025-40202 https://www.cve.org/CVERecord?id=CVE-2025-40202 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=CVE-2025-40204 Référence CVE CVE-2025-40205 https://www.cve.org/CVERecord?id=CVE-2025-40205 Référence CVE CVE-2025-40206 https://www.cve.org/CVERecord?id=CVE-2025-40206 Référence CVE CVE-2025-40207 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40018 Référence CVE CVE-2025-40019 https://www.cve.org/CVERecord?id=CVE-2025-40019 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40130 https://www.cve.org/CVERecord?id=CVE-2025-40130 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=CVE-2025-40170 Référence CVE CVE-2025-40179 https://www.cve.org/CVERecord?id=CVE-2025-40179 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=CVE-2025-40204 Référence CVE CVE-2025-40209 https://www.cve.org/CVERecord?id=CVE-2025-40209 Référence CVE CVE-2025-40211 https://www.cve.org/CVERecord?id=CVE-2025-40211 Référence CVE CVE-2025-40212 https://www.cve.org/CVERecord?id=CVE-2025-40212 Référence CVE CVE-2025-40213 https://www.cve.org/CVERecord?id=CVE-2025-40213 Référence CVE CVE-2025-40214 https://www.cve.org/CVERecord?id=CVE-2025-40214 Référence CVE CVE-2025-40215 https://www.cve.org/CVERecord?id=CVE-2025-40215 Référence CVE CVE-2025-40218 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40158 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-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=CVE-2025-40170 Référence CVE CVE-2025-40178 https://www.cve.org/CVERecord?id=CVE-2025-40178 Référence CVE CVE-2025-40179 https://www.cve.org/CVERecord?id=CVE-2025-40179 Référence CVE CVE-2025-40187 https://www.cve.org/CVERecord?id=CVE-2025-40187 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40198 https://www.cve.org/CVERecord?id=CVE-2025-40198 Référence CVE CVE-2025-40200 https://www.cve.org/CVERecord?id=CVE-2025-40200 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=CVE-2025-40204 Référence CVE CVE-2025-40211 https://www.cve.org/CVERecord?id=CVE-2025-40211 Référence CVE CVE-2025-40212 https://www.cve.org/CVERecord?id=CVE-2025-40212 Référence CVE CVE-2025-40213 https://www.cve.org/CVERecord?id=CVE-2025-40213 Référence CVE CVE-2025-40215 https://www.cve.org/CVERecord?id=CVE-2025-40215 Référence CVE CVE-2025-40219 https://www.cve.org/CVERecord?id=

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

d?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-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40173 https://www.cve.org/CVERecord?id=CVE-2025-40173 Référence CVE CVE-2025-40178 https://www.cve.org/CVERecord?id=CVE-2025-40178 Référence CVE CVE-2025-40183 https://www.cve.org/CVERecord?id=CVE-2025-40183 Référence CVE CVE-2025-40186 https://www.cve.org/CVERecord?id=CVE-2025-40186 Référence CVE CVE-2025-40187 https://www.cve.org/CVERecord?id=CVE-2025-40187 Référence CVE CVE-2025-40188 https://www.cve.org/CVERecord?id=CVE-2025-40188 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40194 https://www.cve.org/CVERecord?id=CVE-2025-40194 Référence CVE CVE-2025-40197 https://www.cve.org/CVERecord?id=CVE-2025-40197 Référence CVE CVE-2025-40198 https://www.cve.org/CVERecord?id=CVE-2025-40198 Référence CVE CVE-2025-40200 https://www.cve.org/CVERecord?id=CVE-2025-40200 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=CVE-2025-40204 Référence CVE CVE-2025-40205 https://www.cve.org/CVERecord?id=CVE-2025-40205 Référence CVE CVE-2025-40211 https://www.cve.org/CVERecord?id=CVE-2025-40211 Référence CVE CVE-2025-40219 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40171 Référence CVE CVE-2025-40173 https://www.cve.org/CVERecord?id=CVE-2025-40173 Référence CVE CVE-2025-40176 https://www.cve.org/CVERecord?id=CVE-2025-40176 Référence CVE CVE-2025-40178 https://www.cve.org/CVERecord?id=CVE-2025-40178 Référence CVE CVE-2025-40179 https://www.cve.org/CVERecord?id=CVE-2025-40179 Référence CVE CVE-2025-40183 https://www.cve.org/CVERecord?id=CVE-2025-40183 Référence CVE CVE-2025-40186 https://www.cve.org/CVERecord?id=CVE-2025-40186 Référence CVE CVE-2025-40187 https://www.cve.org/CVERecord?id=CVE-2025-40187 Référence CVE CVE-2025-40188 https://www.cve.org/CVERecord?id=CVE-2025-40188 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40193 https://www.cve.org/CVERecord?id=CVE-2025-40193 Référence CVE CVE-2025-40194 https://www.cve.org/CVERecord?id=CVE-2025-40194 Référence CVE CVE-2025-40197 https://www.cve.org/CVERecord?id=CVE-2025-40197 Référence CVE CVE-2025-40198 https://www.cve.org/CVERecord?id=CVE-2025-40198 Référence CVE CVE-2025-40200 https://www.cve.org/CVERecord?id=CVE-2025-40200 Référence CVE CVE-2025-40201 https://www.cve.org/CVERecord?id=CVE-2025-40201 Référence CVE CVE-2025-40202 https://www.cve.org/CVERecord?id=CVE-2025-40202 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6641MS 12월 보안 위협에 따른 정기 보안 업데이트 권고

| | Mariner | CVE-2025-40200 | Squashfs: reject negative file sizes in squashfs_read_inode() | | Mariner | CVE-2025-40198 | ext4: avoid potential buffer over-read in parse_apply_sb_mount_options() | | Mariner | CVE-2025-40197 | media: mc: Clear minor number before put device | | Mariner | CVE-2025-40195 | mount: handle NULL values in mnt_ns_release() | | Mariner | CVE-2025-40194 | cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() | | Mariner | CVE-2025-40193 | xtensa: simdisk: add input size check in proc_write_simdisk | | Mariner | CVE-2025-40192 | Revert "ipmi: fix msg stack when IPMI is disconnected" | | Mariner | CVE-2025-40190 | ext4: guard against EA inode refcount underflow in xattr update | | Mariner | CVE-2025-40188 | pwm: berlin: Fix wrong register in suspend/resume | | Mariner | CVE-2025-40187 | net/sctp: fix a null dereference in sctp_disposition sctp_sf_do_5_1D_ce() | | Mariner | CVE-2025-40180 | mailbox: zynqmp-ipi: Fix out-of-bounds access in mailbox cleanup loop | | Mariner | CVE-2025-40179 | ext4: verify orphan file size is not too big | | Mariner | CVE-2025-40178 | pid: Add a judgment for ns null in pid_nr_ns | | Mariner | CVE-2025-40176 | tls: wait for pending async decryptions if tls_strp_msg_hold fails | | Mariner | CVE-2025-40173 | net/ip6_tunnel:

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.4.301 ≤ 5.4.*, 5.10.246 ≤ 5.10.*, 5.15.195 ≤ 5.15.*, 6.1.157 ≤ 6.1.*, 6.6.113 ≤ 6.6.*, 6.12.54 ≤ 6.12.*, 6.17.4 ≤ 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-150384
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-150384↗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-40190 · cve.blacktree.nl