nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode()
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.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 116d53f09ff52e6f98e3fe1f85d8898d6ba26c68, 2a782ea8ebd712a458466e3103e2881b4f886cb5, 6b4205ea97901f822004e6c8d59484ccfda03faa.
Low priority for now. Upgrade to Linux Linux 116d53f09ff52e6f98e3fe1f85d8898d6ba26c68, 2a782ea8ebd712a458466e3103e2881b4f886cb5, 6b4205ea97901f822004e6c8d59484ccfda03faa 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: nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode() During unmount process of nilfs2, nothing holds nilfs_root structure after nilfs2 detaches its writer in nilfs_detach_log_writer(). However, since nilfs_evict_inode() uses nilfs_root for some cleanup operations, it may cause use-after-free read if inodes are left in "garbage_list" and released by nilfs_dispose_list() at the end of nilfs_detach_log_writer(). Fix this issue by modifying nilfs_evict_inode() to only clear inode without additional metadata changes that use nilfs_root if the file system is degraded to read-only or the writer is detached.
- Published
- Dec 8, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 2th 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
- 2.6.37affected
- e912a5b66837ee89fb025e67b5efeaa11930c2ce and later · before f31e18131ee2ce80a4da5c808221d25b1ae9ad6daffected · git
- e912a5b66837ee89fb025e67b5efeaa11930c2ce and later · before 2a782ea8ebd712a458466e3103e2881b4f886cb5affected · git
- e912a5b66837ee89fb025e67b5efeaa11930c2ce and later · before 116d53f09ff52e6f98e3fe1f85d8898d6ba26c68affected · git
- e912a5b66837ee89fb025e67b5efeaa11930c2ce and later · before 6b4205ea97901f822004e6c8d59484ccfda03faaaffected · git
- e912a5b66837ee89fb025e67b5efeaa11930c2ce and later · before b8427b8522d9ede53015ba45a9978ba68d1162f5affected · git
- e912a5b66837ee89fb025e67b5efeaa11930c2ce and later · before acc2a40e428f12780004e1e9fce4722d88f909fdaffected · git
- e912a5b66837ee89fb025e67b5efeaa11930c2ce and later · before fb8e8d58f116d069e5939e1f786ac84e7fa4533eaffected · git
- e912a5b66837ee89fb025e67b5efeaa11930c2ce and later · before 9b5a04ac3ad9898c4745cba46ea26de74ba56a8eaffected · git
- before 2.6.37not affected · 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.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
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-2023-53801Dec 8, 2025 · iommu/sprd: Release dma buffer to avoid memory leak0Monitor
- ← EarlierCVE-2023-53802Dec 8, 2025 · wifi: ath9k: htc_hst: free skb in ath9k_htc_rx_msg() if there is no callback function0Monitor
- Later →CVE-2023-53806Dec 8, 2025 · drm/amd/display: populate subvp cmd info only for the top pipe31Monitor
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 | 116d53f09ff52e6f98e3fe1f85d8898d6ba26c68 | Vendor (CNA) |
| Linux Linux | 2a782ea8ebd712a458466e3103e2881b4f886cb5 | Vendor (CNA) |
| Linux Linux | 6b4205ea97901f822004e6c8d59484ccfda03faa | Vendor (CNA) |
| Linux Linux | 9b5a04ac3ad9898c4745cba46ea26de74ba56a8e | Vendor (CNA) |
| Linux Linux | acc2a40e428f12780004e1e9fce4722d88f909fd | Vendor (CNA) |
| Linux Linux | b8427b8522d9ede53015ba45a9978ba68d1162f5 | Vendor (CNA) |
| Linux Linux | f31e18131ee2ce80a4da5c808221d25b1ae9ad6d | Vendor (CNA) |
| Linux Linux | fb8e8d58f116d069e5939e1f786ac84e7fa4533e | Vendor (CNA) |
| debian:linux | 6.1.37-1 · Debian:12 | Package registry (OSV) |
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- A low-privileged account is enough.
- No user action is required.
- 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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/2a782ea8ebd712a458466e3103e2881b4f886cb5
- git.kernel.org/stable/c/6b4205ea97901f822004e6c8d59484ccfda03faa
- git.kernel.org/stable/c/9b5a04ac3ad9898c4745cba46ea26de74ba56a8e
- git.kernel.org/stable/c/acc2a40e428f12780004e1e9fce4722d88f909fd
- git.kernel.org/stable/c/b8427b8522d9ede53015ba45a9978ba68d1162f5
- git.kernel.org/stable/c/f31e18131ee2ce80a4da5c808221d25b1ae9ad6d
- git.kernel.org/stable/c/fb8e8d58f116d069e5939e1f786ac84e7fa4533e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.