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-26696nilfs2: fix hang in nilfs_lookup_dirty_data_buffers()

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause is that the wait for writeback completion in nilfs_page_mkwrite() is conditional, and if the backing device does not require stable writes, data may be modified without waiting. Fix these issues by making nilfs_page_mkwrite() wait for writeback to finish regardless of the stable write requirement of the backing device.

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-26696, by who scored it
Scored byCVSSScoreVector
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.19% · top 91% of all CVEs (17 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 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – < 228742b2ddfb99dfd71e5a307e6088ab6836272e
    • affected 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – < 862ee4422c38be5c249844a684b00d0dbe9d1e46
    • affected 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – < 98a4026b22ff440c7f47056481bcbbe442f607d6
    • affected 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – < 7e9b622bd0748cc104d66535b76d9b3535f9dc0f
    • affected 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – < 8494ba2c9ea00a54d5b50e69b22c55a8958bce32
    • affected 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – < ea5ddbc11613b55e5128c85f57b08f907abd9b28
    • affected 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – < e38585401d464578d30f5868ff4ca54475c34f7d
    • affected 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 – < 38296afe3c6ee07319e01bb249aa4bb47c07b534
  • Linux · Linux

    • affected 3.9
    • unaffected < 3.9
    • 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-26696 badge
[![CVE-2024-26696](https://cveledger.app/badge/CVE-2024-26696.svg)](https://cveledger.app/cve/CVE-2024-26696)

Record last updated .