CVE-2025-40190: ext4: guard against EA inode refcount underflow in xattr update
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1cfb3e4ddbdc8e02e637b8852540bd4718bf4814, 3d6269028246f4484bfed403c947a114bb583631, 440b003f449a4ff2a00b08c8eab9ba5cd28f3943; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1.
Low priority for now. Upgrade to Linux Linux 1cfb3e4ddbdc8e02e637b8852540bd4718bf4814, 3d6269028246f4484bfed403c947a114bb583631, 440b003f449a4ff2a00b08c8eab9ba5cd28f3943; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 12, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ea39e712c2f5ae148ee5515798ae03523673e002affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1cfb3e4ddbdc8e02e637b8852540bd4718bf4814affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 505e69f76ac497e788f4ea0267826ec7266b40c8affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3d6269028246f4484bfed403c947a114bb583631affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 79ea7f3e11effe1bd9e753172981d9029133a278affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6b879c4c6bbaab03c0ad2a983953bd1410bb165eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 440b003f449a4ff2a00b08c8eab9ba5cd28f3943affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 57295e835408d8d425bef58da5253465db3d6888affected · git
- before 5.4.301affected · semver
- before 5.10.246affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.158-1 | 6.1.158-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.9.1.160000.2.6 | 6.12.0-160000.9.1.160000.2.6 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-azure | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-syms | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
+4
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40188Nov 12, 2025 · pwm: berlin: Fix wrong register in suspend/resume0Monitor
- ← EarlierCVE-2025-40189Nov 12, 2025 · net: usb: lan78xx: Fix lost EEPROM read timeout error(-ETIMEDOUT) in lan78xx_read_raw_eeprom0Monitor
- Later →CVE-2025-40191Nov 12, 2025 · drm/amdkfd: Fix kfd process ref leaking when userptr unmapping0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1cfb3e4ddbdc8e02e637b8852540bd4718bf4814 | Vendor (CNA) |
| Linux Linux | 3d6269028246f4484bfed403c947a114bb583631 | Vendor (CNA) |
| Linux Linux | 440b003f449a4ff2a00b08c8eab9ba5cd28f3943 | Vendor (CNA) |
| Linux Linux | 5.10.246 | Vendor (CNA) |
| Linux Linux | 5.15.195 | Vendor (CNA) |
| Linux Linux | 5.4.301 | Vendor (CNA) |
| Linux Linux | 505e69f76ac497e788f4ea0267826ec7266b40c8 | Vendor (CNA) |
| Linux Linux | 57295e835408d8d425bef58da5253465db3d6888 | Vendor (CNA) |
| Linux Linux | 6.1.157 | Vendor (CNA) |
| Linux Linux | 6.12.54 | Vendor (CNA) |
| Linux Linux | 6.17.4 | Vendor (CNA) |
| Linux Linux | 6.6.113 | Vendor (CNA) |
| Linux Linux | 6b879c4c6bbaab03c0ad2a983953bd1410bb165e | Vendor (CNA) |
| Linux Linux | 79ea7f3e11effe1bd9e753172981d9029133a278 | Vendor (CNA) |
| Linux Linux | ea39e712c2f5ae148ee5515798ae03523673e002 | Vendor (CNA) |
| azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 | 6.6.117.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.158-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.9.1.160000.2.6 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
+11
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3d6269028246f4484bfed403c947a114bb583631
- git.kernel.org/stable/c/440b003f449a4ff2a00b08c8eab9ba5cd28f3943
- git.kernel.org/stable/c/505e69f76ac497e788f4ea0267826ec7266b40c8
- git.kernel.org/stable/c/57295e835408d8d425bef58da5253465db3d6888
- git.kernel.org/stable/c/6b879c4c6bbaab03c0ad2a983953bd1410bb165e
- git.kernel.org/stable/c/79ea7f3e11effe1bd9e753172981d9029133a278
- git.kernel.org/stable/c/ea39e712c2f5ae148ee5515798ae03523673e002
Vendor advisories and official records. Exploit/PoC links are deliberately left out.