CVE-2023-54140: nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
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.16% (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 46c11be2dca295742a5508ea910a77f7733fb7f4, 473795610594f261e98920f0945550314df36f07, 4da07e958bfda2d69d83db105780e8916e3ac02e.
Low priority for now. Upgrade to Linux Linux 46c11be2dca295742a5508ea910a77f7733fb7f4, 473795610594f261e98920f0945550314df36f07, 4da07e958bfda2d69d83db105780e8916e3ac02e 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 WARNING in mark_buffer_dirty due to discarded buffer reuse A syzbot stress test using a corrupted disk image reported that mark_buffer_dirty() called from __nilfs_mark_inode_dirty() or nilfs_palloc_commit_alloc_entry() may output a kernel warning, and can panic if the kernel is booted with panic_on_warn. This is because nilfs2 keeps buffer pointers in local structures for some metadata and reuses them, but such buffers may be forcibly discarded by nilfs_clear_dirty_page() in some critical situations. This issue is reported to appear after commit 28a65b49eb53 ("nilfs2: do not write dirty data after degenerating to read-only"), but the issue has potentially existed before. Fix this issue by checking the uptodate flag when attempting to reuse an internally held buffer, and reloading the metadata instead of reusing the buffer if the flag was lost.
- Published
- Dec 24, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 5th 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
- 3.10affected
- 8c26c4e2694a163d525976e804d81cd955bbb40c and later · before 473795610594f261e98920f0945550314df36f07affected · git
- 8c26c4e2694a163d525976e804d81cd955bbb40c and later · before d95e403588738c7ec38f52b9f490b15e7745d393affected · git
- 8c26c4e2694a163d525976e804d81cd955bbb40c and later · before 99a73016a5e12a09586a96f998e91f9ea145cd00affected · git
- 8c26c4e2694a163d525976e804d81cd955bbb40c and later · before f1d637b63d8a27ac3386f186a694907f2717fc13affected · git
- 8c26c4e2694a163d525976e804d81cd955bbb40c and later · before b911bef132a06de01a745c6a24172d6db7216333affected · git
- 8c26c4e2694a163d525976e804d81cd955bbb40c and later · before 4da07e958bfda2d69d83db105780e8916e3ac02eaffected · git
- 8c26c4e2694a163d525976e804d81cd955bbb40c and later · before 46c11be2dca295742a5508ea910a77f7733fb7f4affected · git
- 8c26c4e2694a163d525976e804d81cd955bbb40c and later · before b308b3eabc429649b5501d36290cea403fbd746caffected · git
- 8c26c4e2694a163d525976e804d81cd955bbb40c and later · before cdaac8e7e5a059f9b5e816cda257f08d0abffacdaffected · git
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.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.5.3-1 | 6.5.3-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-54138Dec 24, 2025 · drm/msm: fix NULL-deref on irq uninstall0Monitor
- ← EarlierCVE-2023-54139Dec 24, 2025 · tracing/user_events: Ensure write index cannot be negative31Monitor
- Later →CVE-2023-54141Dec 24, 2025 · wifi: ath11k: Add missing hw_ops->get_ring_selector() for IPQ50180Monitor
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 | 46c11be2dca295742a5508ea910a77f7733fb7f4 | Vendor (CNA) |
| Linux Linux | 473795610594f261e98920f0945550314df36f07 | Vendor (CNA) |
| Linux Linux | 4da07e958bfda2d69d83db105780e8916e3ac02e | Vendor (CNA) |
| Linux Linux | 99a73016a5e12a09586a96f998e91f9ea145cd00 | Vendor (CNA) |
| Linux Linux | b308b3eabc429649b5501d36290cea403fbd746c | Vendor (CNA) |
| Linux Linux | b911bef132a06de01a745c6a24172d6db7216333 | Vendor (CNA) |
| Linux Linux | cdaac8e7e5a059f9b5e816cda257f08d0abffacd | Vendor (CNA) |
| Linux Linux | d95e403588738c7ec38f52b9f490b15e7745d393 | Vendor (CNA) |
| Linux Linux | f1d637b63d8a27ac3386f186a694907f2717fc13 | Vendor (CNA) |
| debian:linux | 6.1.52-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.
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.
- 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 (8 more)Show less
- git.kernel.org/stable/c/473795610594f261e98920f0945550314df36f07
- git.kernel.org/stable/c/4da07e958bfda2d69d83db105780e8916e3ac02e
- git.kernel.org/stable/c/99a73016a5e12a09586a96f998e91f9ea145cd00
- git.kernel.org/stable/c/b308b3eabc429649b5501d36290cea403fbd746c
- git.kernel.org/stable/c/b911bef132a06de01a745c6a24172d6db7216333
- git.kernel.org/stable/c/cdaac8e7e5a059f9b5e816cda257f08d0abffacd
- git.kernel.org/stable/c/d95e403588738c7ec38f52b9f490b15e7745d393
- git.kernel.org/stable/c/f1d637b63d8a27ac3386f186a694907f2717fc13
Vendor advisories and official records. Exploit/PoC links are deliberately left out.