CVE-2023-53337
published 2025-09-17CVE-2023-53337: 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…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.19%
8.8th percentile
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
23 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.37-1 (bookworm) | linux 6.1.37-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 8c26c4e2694a163d525976e804d81cd955bbb40c < bd89073fc7a5d03b1d06b372addbe405e5a925f4 | bd89073fc7a5d03b1d06b372addbe405e5a925f4 |
| linux | linux | >= 8c26c4e2694a163d525976e804d81cd955bbb40c < e9c5412c5972124776c1b873533eb39e287a4dfa | e9c5412c5972124776c1b873533eb39e287a4dfa |
| linux | linux | >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 4569a292a84e340e97d178898ad1cfe1a3080a61 | 4569a292a84e340e97d178898ad1cfe1a3080a61 |
| linux | linux | >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 7c3e662048053802f6b0db3a78e97f4e1f7edc4f | 7c3e662048053802f6b0db3a78e97f4e1f7edc4f |
| linux | linux | >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 13f73ef77baa4764dc1ca4fcbae9cade05b83866 | 13f73ef77baa4764dc1ca4fcbae9cade05b83866 |
| linux | linux | >= 8c26c4e2694a163d525976e804d81cd955bbb40c < a73201c607d8e506358d60aafddda4246bdd9350 | a73201c607d8e506358d60aafddda4246bdd9350 |
| linux | linux | >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 4005cec6847c06ee191583270b7cdd7e696543cc | 4005cec6847c06ee191583270b7cdd7e696543cc |
| linux | linux | >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 55f7810632f993cff622a0ddbc7c865892294b61 | 55f7810632f993cff622a0ddbc7c865892294b61 |
| linux | linux | >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 28a65b49eb53e172d23567005465019658bfdb4d | 28a65b49eb53e172d23567005465019658bfdb4d |
| linux | linux_kernel | < 4.14.315 | 4.14.315 |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| linux | linux_kernel | >= 0 < 6.1.37-1 | 6.1.37-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 4.15 < 4.19.283 | 4.19.283 |
| linux | linux_kernel | >= 4.20 < 5.4.243 | 5.4.243 |
| linux | linux_kernel | >= 5.11 < 5.15.111 | 5.15.111 |
| linux | linux_kernel | >= 5.16 < 6.1.28 | 6.1.28 |
| linux | linux_kernel | >= 5.5 < 5.10.180 | 5.10.180 |
| linux | linux_kernel | >= 6.2 < 6.2.15 | 6.2.15 |
| linux | linux_kernel | >= 6.3 < 6.3.2 | 6.3.2 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: nilfs2: do not write dirty data after degenerating to read-only
vendor_redhat·2025-09-17·CVSS 5.5
CVE-2023-53337 [MEDIUM] kernel: nilfs2: do not write dirty data after degenerating to read-only
kernel: nilfs2: do not write dirty data after degenerating to read-only
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 sho
Debian
CVE-2023-53337: linux - In the Linux kernel, the following vulnerability has been resolved: nilfs2: do ...
vendor_debian·2023·CVSS 5.5
CVE-2023-53337 [MEDIUM] CVE-2023-53337: linux - In the Linux kernel, the following vulnerability has been resolved: nilfs2: do ...
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
OSV
CVE-2023-53337: In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbo
osv·2025-09-17·CVSS 5.5
CVE-2023-53337 [MEDIUM] CVE-2023-53337: In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbo
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
GHSA
GHSA-jvhc-rq6w-32mx: In the Linux kernel, the following vulnerability has been resolved:
nilfs2: do not write dirty data after degenerating to read-only
According to syz
ghsa_unreviewed·2025-09-17
CVE-2023-53337 [MEDIUM] GHSA-jvhc-rq6w-32mx: In the Linux kernel, the following vulnerability has been resolved:
nilfs2: do not write dirty data after degenerating to read-only
According to syz
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 f
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/13f73ef77baa4764dc1ca4fcbae9cade05b83866https://git.kernel.org/stable/c/28a65b49eb53e172d23567005465019658bfdb4dhttps://git.kernel.org/stable/c/4005cec6847c06ee191583270b7cdd7e696543cchttps://git.kernel.org/stable/c/4569a292a84e340e97d178898ad1cfe1a3080a61https://git.kernel.org/stable/c/55f7810632f993cff622a0ddbc7c865892294b61https://git.kernel.org/stable/c/7c3e662048053802f6b0db3a78e97f4e1f7edc4fhttps://git.kernel.org/stable/c/a73201c607d8e506358d60aafddda4246bdd9350https://git.kernel.org/stable/c/bd89073fc7a5d03b1d06b372addbe405e5a925f4https://git.kernel.org/stable/c/e9c5412c5972124776c1b873533eb39e287a4dfa
2025-09-17
Published