CVE-2023-54140

nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse

HIGH
7.8
CVSS Score
Published: December 24, 2025 at 01:06 PM UTC
Updated: August 5, 2026 at 10:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.10 ≤ v < 4.14.3263.10 ≤ v < 4.19.2953.10 ≤ v < 5.10.1953.10 ≤ v < 5.15.1313.10 ≤ v < 5.4.2573.10 ≤ v < 6.1.523.10 ≤ v < 6.4.153.10 ≤ v < 6.5.23.10 ≤ v < 6.63.108c26c4e2694a163d525976e804d81cd955bbb40c
Vendor states this is fixed in 46c11be2dca295742a5508ea910a77f7733fb7f4 (fixed)
Vendor states this is fixed in 473795610594f261e98920f0945550314df36f07 (fixed)
Vendor states this is fixed in 4da07e958bfda2d69d83db105780e8916e3ac02e (fixed)
Vendor states this is fixed in 99a73016a5e12a09586a96f998e91f9ea145cd00 (fixed)
Vendor states this is fixed in b308b3eabc429649b5501d36290cea403fbd746c (fixed)
Vendor states this is fixed in b911bef132a06de01a745c6a24172d6db7216333 (fixed)
Vendor states this is fixed in cdaac8e7e5a059f9b5e816cda257f08d0abffacd (fixed)
Vendor states this is fixed in d95e403588738c7ec38f52b9f490b15e7745d393 (fixed)
Vendor states this is fixed in f1d637b63d8a27ac3386f186a694907f2717fc13 (fixed)
Vendor states this is fixed in 3.10 (unaffected)
Vendor states this is fixed in 4.14.326 (unaffected)
Vendor states this is fixed in 4.19.295 (unaffected)
Vendor states this is fixed in 5.10.195 (unaffected)
Vendor states this is fixed in 5.15.131 (unaffected)
Vendor states this is fixed in 5.4.257 (unaffected)
Vendor states this is fixed in 6.1.52 (unaffected)
Vendor states this is fixed in 6.4.15 (unaffected)
Vendor states this is fixed in 6.5.2 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (9)

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card