Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-53337

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

Medium5.5EPSS 0.21%
Published
Updated
Reserved
Assigned by
Linux

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53337, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

  • CWE-noinfo Not enough information

Affected products

  • Linux · Linux

    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < bd89073fc7a5d03b1d06b372addbe405e5a925f4
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < e9c5412c5972124776c1b873533eb39e287a4dfa
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 4569a292a84e340e97d178898ad1cfe1a3080a61
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 7c3e662048053802f6b0db3a78e97f4e1f7edc4f
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 13f73ef77baa4764dc1ca4fcbae9cade05b83866
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < a73201c607d8e506358d60aafddda4246bdd9350
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 4005cec6847c06ee191583270b7cdd7e696543cc
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 55f7810632f993cff622a0ddbc7c865892294b61
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 28a65b49eb53e172d23567005465019658bfdb4d
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 4.14.315 – ≤ 4.14.*
    • unaffected 4.19.283 – ≤ 4.19.*
    • unaffected 5.4.243 – ≤ 5.4.*
    • unaffected 5.10.180 – ≤ 5.10.*
    • unaffected 5.15.111 – ≤ 5.15.*
    • unaffected 6.1.28 – ≤ 6.1.*
    • unaffected 6.2.15 – ≤ 6.2.*
    • unaffected 6.3.2 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53337 badge
[![CVE-2023-53337](https://trackcve.app/badge/CVE-2023-53337.svg)](https://trackcve.app/cve/CVE-2023-53337)

Record last updated .