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-37078nilfs2: fix potential kernel bug due to lack of writeback flag waiting

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential kernel bug due to lack of writeback flag waiting Destructive writes to a block device on which nilfs2 is mounted can cause a kernel bug in the folio/page writeback start routine or writeback end routine (__folio_start_writeback in the log below): kernel BUG at mm/page-writeback.c:3070! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI ... RIP: 0010:__folio_start_writeback+0xbaa/0x10e0 Code: 25 ff 0f 00 00 0f 84 18 01 00 00 e8 40 ca c6 ff e9 17 f6 ff ff e8 36 ca c6 ff 4c 89 f7 48 c7 c6 80 c0 12 84 e8 e7 b3 0f 00 90 <0f> 0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00 ... Call Trace: <TASK> nilfs_segctor_do_construct+0x4654/0x69d0 [nilfs2] nilfs_segctor_construct+0x181/0x6b0 [nilfs2] nilfs_segctor_thread+0x548/0x11c0 [nilfs2] kthread+0x2f0/0x390 ret_from_fork+0x4b/0x80 ret_from_fork_asm+0x1a/0x30 </TASK> This is because when the log writer starts a writeback for segment summary blocks or a super root block that use the backing device's page cache, it does not wait for the ongoing folio/page writeback, resulting in an inconsistent writeback state. Fix this issue by waiting for ongoing writebacks when putting folios/pages on the backing device into writeback state.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day 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-37078, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS (exploitation in 30 days)
0.26% · top 83% 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: High 7.8.

Affected products

  • Linux · Linux

    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 95f6f81e50d858a7c9aa7c795ec14a0ac3819118
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < a75b8f493dfc48aa38c518430bd9e03b53bffebe
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 0ecfe3a92869a59668d27228dabbd7965e83567f
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 33900d7eae616647e179eee1c66ebe654ee39627
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 271dcd977ccda8c7a26e360425ae7b4db7d2ecc0
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 614d397be0cf43412b3f94a0f6460eddced8ce92
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < a4ca369ca221bb7e06c725792ac107f0e48e82e7
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 4.19.317 – ≤ 4.19.*
    • unaffected 5.4.279 – ≤ 5.4.*
    • unaffected 5.10.221 – ≤ 5.10.*
    • unaffected 5.15.162 – ≤ 5.15.*
    • unaffected 6.1.95 – ≤ 6.1.*
    • unaffected 6.6.35 – ≤ 6.6.*
    • unaffected 6.9.5 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .