Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26685nilfs2: fix potential bug in end_buffer_async_write

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential bug in end_buffer_async_write According to a syzbot report, end_buffer_async_write(), which handles the completion of block device writes, may detect abnormal condition of the buffer async_write flag and cause a BUG_ON failure when using nilfs2. Nilfs2 itself does not use end_buffer_async_write(). But, the async_write flag is now used as a marker by commit 7f42ec394156 ("nilfs2: fix issue with race condition of competition between segments for dirty blocks") as a means of resolving double list insertion of dirty blocks in nilfs_lookup_dirty_data_buffers() and nilfs_lookup_node_buffers() and the resulting crash. This modification is safe as long as it is used for file data and b-tree node blocks where the page caches are independent. However, it was irrelevant and redundant to also introduce async_write for segment summary and super root blocks that share buffers with the backing device. This led to the possibility that the BUG_ON check in end_buffer_async_write would fail as described above, if independent writebacks of the backing device occurred in parallel. The use of async_write for segment summary buffers has already been removed in a previous change. Fix this issue by removing the manipulation of the async_write flag for the remaining super root block buffer.

Timeline

  1. ID reserved

    By Linux

  2. · 44 days later

    Published

  3. · 2 years 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-2024-26685, 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 · Analyzed3.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.25% · top 84% of all CVEs (16 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.

Affected products

  • Linux · Linux

    • affected 7f42ec3941560f0902fe3671e36f2c20ffd3af0a – < c4a09fdac625e64abe478dcf88bfa20406616928
    • affected 7f42ec3941560f0902fe3671e36f2c20ffd3af0a – < d31c8721e816eff5ca6573cc487754f357c093cd
    • affected 7f42ec3941560f0902fe3671e36f2c20ffd3af0a – < f3e4963566f58726d3265a727116a42b591f6596
    • affected 7f42ec3941560f0902fe3671e36f2c20ffd3af0a – < 8fa90634ec3e9cc50f42dd605eec60f2d146ced8
    • affected 7f42ec3941560f0902fe3671e36f2c20ffd3af0a – < 6589f0f72f8edd1fa11adce4eedbd3615f2e78ab
    • affected 7f42ec3941560f0902fe3671e36f2c20ffd3af0a – < 2c3bdba00283a6c7a5b19481a59a730f46063803
    • affected 7f42ec3941560f0902fe3671e36f2c20ffd3af0a – < 626daab3811b772086aef1bf8eed3ffe6f523eff
    • affected 7f42ec3941560f0902fe3671e36f2c20ffd3af0a – < 5bc09b397cbf1221f8a8aacb1152650c9195b02b
    • affected ccebcc74c81d8399c7b204aea47c1f33b09c2b17
    • affected 831c87640d23ccb253a02e4901bd9a325b5e8c2d
    • affected d8974c7fe717ee8fb0706e35cc92e0bcdf660ec5
    • affected 8f67918af09fc0ffd426a9b6f87697976d3fbc7b
    • affected 3.2.52 – < 3.3
    • affected 3.4.83 – < 3.5
    • affected 3.10.16 – < 3.11
    • affected 3.11.5 – < 3.12
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 4.19.307 – ≤ 4.19.*
    • unaffected 5.4.269 – ≤ 5.4.*
    • unaffected 5.10.210 – ≤ 5.10.*
    • unaffected 5.15.149 – ≤ 5.15.*
    • unaffected 6.1.79 – ≤ 6.1.*
    • unaffected 6.6.18 – ≤ 6.6.*
    • unaffected 6.7.6 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

CVE-2024-26685 badge
[![CVE-2024-26685](https://cveledger.app/badge/CVE-2024-26685.svg)](https://cveledger.app/cve/CVE-2024-26685)

Record last updated .