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 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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.315, 4.19.283, 5.10.180, 5.15.111, 5.4.243, 6.1.28, 6.2.15, 6.3.2
- CVEs
- CVE-2023-53337
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 02:51 UTC · Revision 1
Source evidence
nilfs2: do not write dirty data after degenerating to read-only
core-osv · Original sourcePublished 17 Sept 2025, 14:56 UTC
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.
osv:CVE-2023-53337
Kernel
Fixed versions: 4.14.315, 4.19.283, 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2
Complete source record
{
"id": "fce1a4a68db969b2d9fb3fc45f00beda74e83c8a593312fabc4cd24462661afe",
"url": "https://osv.dev/vulnerability/CVE-2023-53337",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "nilfs2: do not write dirty data after degenerating to read-only",
"summary": "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.",
"evidence": "osv:CVE-2023-53337",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.14.315",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.283",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.243",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.180",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.111",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.28",
"evidence": "/affected/1/ranges"
},
{
"value": "6.2.15",
"evidence": "/affected/1/ranges"
},
{
"value": "6.3.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2023-53337",
"aliases": [
"CVE-2023-53337"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "8c26c4e2694a163d525976e804d81cd955bbb40c"
},
{
"fixed": "bd89073fc7a5d03b1d06b372addbe405e5a925f4"
},
{
"fixed": "e9c5412c5972124776c1b873533eb39e287a4dfa"
},
{
"fixed": "4569a292a84e340e97d178898ad1cfe1a3080a61"
},
{
"fixed": "7c3e662048053802f6b0db3a78e97f4e1f7edc4f"
},
{
"fixed": "13f73ef77baa4764dc1ca4fcbae9cade05b83866"
},
{
"fixed": "a73201c607d8e506358d60aafddda4246bdd9350"
},
{
"fixed": "4005cec6847c06ee191583270b7cdd7e696543cc"
},
{
"fixed": "55f7810632f993cff622a0ddbc7c865892294b61"
},
{
"fixed": "28a65b49eb53e172d23567005465019658bfdb4d"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53337.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.10.0"
},
{
"fixed": "4.14.315"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.283"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.243"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.180"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.111"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.28"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.2.15"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.3.0"
},
{
"fixed": "6.3.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53337.json"
}
}
],
"modified": "2026-10-28T02:30:46.796854600Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/13f73ef77baa4764dc1ca4fcbae9cade05b83866",
"https://git.kernel.org/stable/c/28a65b49eb53e172d23567005465019658bfdb4d",
"https://git.kernel.org/stable/c/4005cec6847c06ee191583270b7cdd7e696543cc",
"https://git.kernel.org/stable/c/4569a292a84e340e97d178898ad1cfe1a3080a61",
"https://git.kernel.org/stable/c/55f7810632f993cff622a0ddbc7c865892294b61",
"https://git.kernel.org/stable/c/7c3e662048053802f6b0db3a78e97f4e1f7edc4f",
"https://git.kernel.org/stable/c/a73201c607d8e506358d60aafddda4246bdd9350",
"https://git.kernel.org/stable/c/bd89073fc7a5d03b1d06b372addbe405e5a925f4",
"https://git.kernel.org/stable/c/e9c5412c5972124776c1b873533eb39e287a4dfa",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53337.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-53337",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53337.json"
}
},
"related_cves": [
{
"value": "CVE-2023-53337",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 514433,
"published_at": "2025-09-17T14:56:31.582+00:00"
}