VDB

CVE-2024-49959

CVE-2024-49959 PUBLISHED

jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error

Reported by linux · Published October 21, 2024

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel-libbpfAmazon Linux6.1.115-126.197.amzn2023
kernel-libbpf-staticAmazon Linux6.1.115-126.197.amzn2023
kernel-modules-extra-commonAmazon Linux6.1.115-126.197.amzn2023
kernel-modules-extraAmazon Linux6.1.115-126.197.amzn2023
perfAmazon Linux6.1.115-126.197.amzn2023
kernelAmazon Linux6.1.115-126.197.amzn2023
python3-perfAmazon Linux6.1.115-126.197.amzn2023
linux_kernellinux6.11.3, 6.10.14, 6.6.55, 6.1.113, 5.15.168, 5.10.227

Affected products

VendorProductVersions
LinuxLinux8c3f25d8950c3e9fe6c9849f88679b3f2a071550, 8c3f25d8950c3e9fe6c9849f88679b3f2a071550, 8c3f25d8950c3e9fe6c9849f88679b3f2a071550
LinuxLinux2.6.28, 0, 4.19.323
amazon:2023kernel-libbpf0
amazon:2023kernel-libbpf-static0
amazon:2023kernel-modules-extra-common0
amazon:2023kernel-modules-extra0
amazon:2023perf0
amazon:2023kernel0
amazon:2023python3-perf0
linuxlinux_kernel2.6.28, 2.6.28, 2.6.28
amazon:2023kernel-livepatch-6.1.115-126.1970
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-devel0
amazon:2023kernel-tools0
amazon:2023bpftool0
amazon:2023kernel-headers0
amazon:2023kernel-tools-devel0
LinuxLinux8c3f25d8950c3e9fe6c9849f88679b3f2a071550, 8c3f25d8950c3e9fe6c9849f88679b3f2a071550, 8c3f25d8950c3e9fe6c9849f88679b3f2a071550

Timeline

  • Oct 21, 2024 CVE Published
  • Oct 22, 2024 EPSS Score (30 in total, the first dated here)
  • Oct 23, 2024 Coalition ESS Score (27 in total, the first dated here)
  • Dec 16, 2025 PoC Published
  • Jan 2, 2026 Security Advisory (475 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (406 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-49959
vulnetix vdb fixes CVE-2024-49959

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-49959/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›