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-49959jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error

Description

In the Linux kernel, the following vulnerability has been resolved: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don't stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain: ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace: <TASK> add_transaction_credits+0x5d1/0x5e0 start_this_handle+0x1ef/0x6a0 jbd2__journal_start+0x18b/0x340 ext4_dirty_inode+0x5d/0xb0 __mark_inode_dirty+0xe4/0x5d0 generic_update_time+0x60/0x70 [...] ============================================ So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways. Note that this fix relies on commit 6f6a6fda2945 ("jbd2: fix ocfs2 corrupt when updating journal superblock fails") to make jbd2_cleanup_journal_tail return the correct error code.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 19 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-2024-49959, by who scored it
Scored byCVSSScoreVector
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.26% · top 82% 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 8c3f25d8950c3e9fe6c9849f88679b3f2a071550 – < 801a35dfef6996f3d5eaa96a59caf00440d9165e
    • affected 8c3f25d8950c3e9fe6c9849f88679b3f2a071550 – < d5dc65370a746750dbb2f03eabcf86b18db65f32
    • affected 8c3f25d8950c3e9fe6c9849f88679b3f2a071550 – < 481e8f18a290e39e04ddb7feb2bb2a2cc3b213ed
    • affected 8c3f25d8950c3e9fe6c9849f88679b3f2a071550 – < ec7f8337c98ad281020ad1f11ba492462d80737a
    • affected 8c3f25d8950c3e9fe6c9849f88679b3f2a071550 – < 70bae48377a2c4296fd3caf4caf8f11079111019
    • affected 8c3f25d8950c3e9fe6c9849f88679b3f2a071550 – < 1c62dc0d82c62f0dc8fcdc4843208e522acccaf5
    • affected 8c3f25d8950c3e9fe6c9849f88679b3f2a071550 – < 3ced0fe6c0eff032733ea8b38778b34707270138
    • affected 8c3f25d8950c3e9fe6c9849f88679b3f2a071550 – < c6bf043b210eac67d35a114e345c4e5585672913
    • affected 8c3f25d8950c3e9fe6c9849f88679b3f2a071550 – < f5cacdc6f2bb2a9bf214469dd7112b43dd2dd68a
  • Linux · Linux

    • affected 2.6.28
    • unaffected < 2.6.28
    • unaffected 4.19.323 – ≤ 4.19.*
    • unaffected 5.4.285 – ≤ 5.4.*
    • unaffected 5.10.227 – ≤ 5.10.*
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.55 – ≤ 6.6.*
    • unaffected 6.10.14 – ≤ 6.10.*
    • unaffected 6.11.3 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .