CVEvulnerability

CVE-2023-53337

5.5 MEDIUM Published 2025-09-17 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2025-09-17
Last modified
2026-06-17
Assigner
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS 3.1 ([email protected])
5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS 3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 configurations

• linux linux kernel (< 4.14.315) • linux linux kernel (>= 4.15 < 4.19.283) • linux linux kernel (>= 4.20 < 5.4.243) • linux linux kernel (>= 5.5 < 5.10.180) • linux linux kernel (>= 5.11 < 5.15.111) • linux linux kernel (>= 5.16 < 6.1.28) • linux linux kernel (>= 6.2 < 6.2.15) • linux linux kernel (>= 6.3 < 6.3.2)

References