Vulnerability · Published Dec 24, 2025 · Assigned by Linux
CVE-2023-54140nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.52-1 | DEBIAN-CVE-2023-54140 |
| Debian:13 | linux | 6.5.3-1 | DEBIAN-CVE-2023-54140 |
| Debian:14 | linux | 6.5.3-1 | DEBIAN-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux | 5.15.0-91.101 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1051.56 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1053.61 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1053.61.1 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1048.56 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1048.53 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1034.40 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1044.47 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1046.52 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1048.53 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-91.101 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1042.42 | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1020.20 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1007.7 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1049.55 | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1044.47 | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-54140 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1027.31 | UBUNTU-CVE-2023-54140 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 8c26c4e2694a163d525976e804d81cd955bbb40c – before 473795610594f261e98920f0945550314df36f078c26c4e2694a163d525976e804d81cd955bbb40c – before d95e403588738c7ec38f52b9f490b15e7745d3938c26c4e2694a163d525976e804d81cd955bbb40c – before 99a73016a5e12a09586a96f998e91f9ea145cd008c26c4e2694a163d525976e804d81cd955bbb40c – before f1d637b63d8a27ac3386f186a694907f2717fc138c26c4e2694a163d525976e804d81cd955bbb40c – before b911bef132a06de01a745c6a24172d6db72163338c26c4e2694a163d525976e804d81cd955bbb40c – before 4da07e958bfda2d69d83db105780e8916e3ac02e8c26c4e2694a163d525976e804d81cd955bbb40c – before 46c11be2dca295742a5508ea910a77f7733fb7f48c26c4e2694a163d525976e804d81cd955bbb40c – before b308b3eabc429649b5501d36290cea403fbd746c |
| Linux | Linux | 3.10 |
References
- https://git.kernel.org/stable/c/473795610594f261e98920f0945550314df36f07
- https://git.kernel.org/stable/c/d95e403588738c7ec38f52b9f490b15e7745d393
- https://git.kernel.org/stable/c/99a73016a5e12a09586a96f998e91f9ea145cd00
- https://git.kernel.org/stable/c/f1d637b63d8a27ac3386f186a694907f2717fc13
- https://git.kernel.org/stable/c/b911bef132a06de01a745c6a24172d6db7216333
- https://git.kernel.org/stable/c/4da07e958bfda2d69d83db105780e8916e3ac02e
- https://git.kernel.org/stable/c/46c11be2dca295742a5508ea910a77f7733fb7f4
- https://git.kernel.org/stable/c/b308b3eabc429649b5501d36290cea403fbd746c
- https://git.kernel.org/stable/c/cdaac8e7e5a059f9b5e816cda257f08d0abffacd