CVE-2026-45942·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: ext4: fix e4b bitmap inconsistency reports A bitmap inconsistency issue was observed during stress tests under mixed huge-page workloads. Ext4 reported multiple e4b bitmap check failures like: ext4_mb_complex_scan_group:2508: group 350, 8179 free clusters as per group info. But got 8192 blocks Analysis and experimentation confirmed that the issue is caused by a race condition between page migration and bitmap modification. Although this timing window is extremely narrow, it is still hit in practice: folio_lock ext4_mb_load_buddy __migrate_folio check ref count folio_mc_copy __filemap_get_folio folio_try_get(folio) ...... mb_mark_used ext4_mb_unload_buddy __folio_migrate_mapping folio_ref_freeze folio_unlock The root cause of this issue is that the fast path of load_buddy only increments the folio's reference count, which is insufficient to prevent concurrent folio migration. We observed that the folio migration process acquires the folio lock. Therefore, we can determine whether to take the fast path in load_buddy by checking the lock status. If the folio is locked, we opt for the slow path (which acquires the lock) to close this concurrency window. Additionally, this change addresses the following issues: When the DOUBLE_CHECK macro is enabled to inspect bitmap-related issues, the following error may be triggered: corruption in group 324 at byte 784(6272): f in copy != ff on disk/prealloc Analysis reveals that this is a false positive. There is a specific race window where the bitmap and the group descriptor become momentarily inconsistent, leading to this error report: ext4_mb_load_buddy ext4_mb_load_buddy __filemap_get_folio(create|lock) folio_lock ext4_mb_init_cache folio_mark_uptodate __filemap_get_folio(no lock) ...... mb_mark_used mb_mark_used_double mb_cmp_bitmaps mb_set_bits(e4b->bd_bitmap) folio_unlock The original logic assumed that since mb_cmp_bitmaps is called when the bitmap is newly loaded from disk, the folio lock would be sufficient to prevent concurrent access. However, this overlooks a specific race condition: if another process attempts to load buddy and finds the folio is already in an uptodate state, it will immediately begin using it without holding folio lock.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.19.4
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.10% — in the bottom 1% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-45942 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.10%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.4
Fixed in: 6.19.4
How to fix this CVE
Update your Linux kernel to version 6.19.4 or later to resolve a race condition in ext4 bitmap handling that causes false inconsistency reports during concurrent page migration and bitmap operations. This patch corrects the synchronization logic in the buddy allocator's load path by checking folio lock status before taking the fast path, eliminating the window where bitmap and group descriptor states can diverge.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check installed kernel version: uname -r | awk -F. '{print $1"."$2"."$3}'
- Verify if kernel is in vulnerable range (6.19.0 to 6.19.3): uname -r | grep -E '^6\.19\.[0-3]'
- Search system logs for ext4 bitmap errors: sudo grep -i 'e4b bitmap\|ext4_mb_complex_scan_group\|bitmap inconsistency' /var/log/kern.log /var/log/messages 2>/dev/null
- After patching, confirm kernel version is 6.19.4 or higher: uname -r and verify output shows version >= 6.19.4
FAQ
What is CVE-2026-45942?
CVE-2026-45942 is a race condition in the Linux kernel's ext4 filesystem buddy allocator that occurs when page migration runs concurrently with bitmap modifications, causing false bitmap inconsistency warnings and potential corruption reports during high-stress workloads with huge pages.
Is CVE-2026-45942 being actively exploited?
No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. It is primarily a reliability and data integrity issue triggered under specific stress conditions.
What versions of Kernel are affected by CVE-2026-45942?
Linux kernel versions 6.19.0 through 6.19.3 are affected. The vulnerability is resolved in kernel version 6.19.4 and later.
How do I check if my server is vulnerable to CVE-2026-45942?
Run `uname -r` to display your kernel version. If the output shows 6.19.0, 6.19.1, 6.19.2, or 6.19.3, your system is vulnerable and should be updated immediately.
Does Defensia detect CVE-2026-45942?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-45942 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/29a07d691d282faf38c33d4b61839b89399110f9
- https://git.kernel.org/stable/c/57e83bfbe1e412ac42daced2086f3c6f9a17bba0
- https://git.kernel.org/stable/c/a3a7d360252c0d84ae8bda067fb296c9e82928d3
- https://git.kernel.org/stable/c/bdc56a9c46b2a99c12313122b9352b619a2e719e
- https://git.kernel.org/stable/c/c05033cfc5c7699cd4df8d48cef94d01da755f24
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-45942. Free for 1 server.
Get started free