CVE-2023-53337

nilfs2: do not write dirty data after degenerating to read-only

MEDIUM
5.5
CVSS Score
Published: September 17, 2025 at 02:56 PM UTC
Updated: June 17, 2026 at 06:44 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
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbot's report, mark_buffer_dirty() called from nilfs_segctor_do_construct() outputs a warning with some patterns after nilfs2 detects metadata corruption and degrades to read-only mode. After such read-only degeneration, page cache data may be cleared through nilfs_clear_dirty_page() which may also clear the uptodate flag for their buffer heads. However, even after the degeneration, log writes are still performed by unmount processing etc., which causes mark_buffer_dirty() to be called for buffer heads without the "uptodate" flag and causes the warning. Since any writes should not be done to a read-only file system in the first place, this fixes the warning in mark_buffer_dirty() by letting nilfs_segctor_do_construct() abort early if in read-only mode. This also changes the retry check of nilfs_segctor_write_out() to avoid unnecessary log write retries if it detects -EROFS that nilfs_segctor_do_construct() returned.

Affected

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

v < 4.14.3153.10 ≤ v < 4.14.3153.10 ≤ v < 4.19.2833.10 ≤ v < 5.10.1803.10 ≤ v < 5.15.1113.10 ≤ v < 5.4.2433.10 ≤ v < 6.1.283.10 ≤ v < 6.2.153.10 ≤ v < 6.3.23.10 ≤ v < 6.44.15 ≤ v < 4.19.2834.20 ≤ v < 5.4.2435.11 ≤ v < 5.15.1115.16 ≤ v < 6.1.285.5 ≤ v < 5.10.1806.2 ≤ v < 6.2.156.3 ≤ v < 6.3.23.108c26c4e2694a163d525976e804d81cd955bbb40c
Vendor states this is fixed in 13f73ef77baa4764dc1ca4fcbae9cade05b83866 (fixed)
Vendor states this is fixed in 28a65b49eb53e172d23567005465019658bfdb4d (fixed)
Vendor states this is fixed in 4005cec6847c06ee191583270b7cdd7e696543cc (fixed)
Vendor states this is fixed in 4569a292a84e340e97d178898ad1cfe1a3080a61 (fixed)
Vendor states this is fixed in 55f7810632f993cff622a0ddbc7c865892294b61 (fixed)
Vendor states this is fixed in 7c3e662048053802f6b0db3a78e97f4e1f7edc4f (fixed)
Vendor states this is fixed in a73201c607d8e506358d60aafddda4246bdd9350 (fixed)
Vendor states this is fixed in bd89073fc7a5d03b1d06b372addbe405e5a925f4 (fixed)
Vendor states this is fixed in e9c5412c5972124776c1b873533eb39e287a4dfa (fixed)
Vendor states this is fixed in 3.10 (unaffected)
Vendor states this is fixed in 4.14.315 (unaffected)
Vendor states this is fixed in 4.19.283 (unaffected)
Vendor states this is fixed in 5.10.180 (unaffected)
Vendor states this is fixed in 5.15.111 (unaffected)
Vendor states this is fixed in 5.4.243 (unaffected)
Vendor states this is fixed in 6.1.28 (unaffected)
Vendor states this is fixed in 6.2.15 (unaffected)
Vendor states this is fixed in 6.3.2 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

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