cve.bz

CVE-2026-45942 linux linux kernel: Race Condition

7.8 highEPSS 0.1%Fix available

High (7.8) in linux linux kernel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-45942 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-45942?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-45942?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-45942 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux2.6.25 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.130
Linux6.126.12.75
Linux6.186.18.14
Linux6.196.19.4
Linuxlater releases7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-45942
Debian13linux6.12.85-1DEBIAN-CVE-2026-45942
Debian14linux6.18.14-1DEBIAN-CVE-2026-45942
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-45942
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-45942
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-45942
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 47 moreno fix listedUBUNTU-CVE-2026-45942
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1061.64~22.04.1UBUNTU-CVE-2026-45942 USN-8595-3
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-45942 USN-8606-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-45942 USN-8609-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1064.72~22.04.1UBUNTU-CVE-2026-45942 USN-8567-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-136.136~22.04.1UBUNTU-CVE-2026-45942 USN-8619-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1061.62~22.04.1UBUNTU-CVE-2026-45942 USN-8574-3
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-136.136.2~22.04.1UBUNTU-CVE-2026-45942 USN-8574-2
Ubuntu22.04:LTSlinux-nvidia-6.86.8.0-1059.62~22.04.1UBUNTU-CVE-2026-45942 USN-8596-1
37 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:8::baseosperf, kernel, bpftool and 30 more0:4.18.0-553.169.1.el8_10RHSA-2026:72468
Red Hatenterprise_linux:8::crbperf-debuginfo, kernel-debuginfo, bpftool-debuginfo and 7 more0:4.18.0-553.169.1.el8_10RHSA-2026:72468
Red Hatenterprise_linux:8::nfvkernel-rt, kernel-rt-kvm, kernel-rt-core and 12 more0:4.18.0-553.169.1.rt7.510.el8_10RHSA-2026:72467
Red Hatenterprise_linux:8::realtimekernel-rt, kernel-rt-core, kernel-rt-debug and 10 more0:4.18.0-553.169.1.rt7.510.el8_10RHSA-2026:72467
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 29 more0:5.14.0-687.53.1.el9_8RHSA-2026:72623
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-687.53.1.el9_8RHSA-2026:72623
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-687.53.1.el9_8RHSA-2026:72623
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-687.53.1.el9_8RHSA-2026:72623
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-64k, kernel-rt-core and 35 more0:5.14.0-687.53.1.el9_8RHSA-2026:72623
Red Hatenterprise_linux:10.2rv, perf, rtla and 87 more0:6.12.0-211.61.1.el10_2RHSA-2026:72624
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.35.1SUSE-SU-2026:22099-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.35.1SUSE-SU-2026:22127-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.35.1.160000.2.16SUSE-SU-2026:22127-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.35.1.160000.2.16SUSE-SU-2026:22112-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.35.1SUSE-SU-2026:22112-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.35.1SUSE-SU-2026:22117-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.35.1.160000.2.16openSUSE-SU-2026:20965-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.35.1openSUSE-SU-2026:20965-1
AlmaLinux8kernel-rt, kernel-rt-core, kernel-rt-debug and 7 more4.18.0-553.169.1.rt7.510.el8_10ALSA-2026:72467
AlmaLinux8perf, kernel, bpftool and 22 more4.18.0-553.169.1.el8_10ALSA-2026:72468
AlmaLinux9rv, perf, rtla and 71 more5.14.0-687.53.1.el9_8ALSA-2026:72623
AlmaLinux10rv, perf, rtla and 72 more6.12.0-211.61.1.el10_2ALSA-2026:72624
Rocky Linux8kernel0:4.18.0-553.169.1.el8_10RLSA-2026:72468
Rocky Linux8kernel-rt0:4.18.0-553.169.1.rt7.510.el8_10RLSA-2026:72467
Rocky Linux9kernel0:5.14.0-687.53.1.el9_8RLSA-2026:72623
Rocky Linux10kernel0:6.12.0-211.61.1.el10_2RLSA-2026:72624
Azure Linux3kernel6.6.139.1-1AZL-88469
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-45942
Alpaquita25linux-lts6.12.80-r0BELL-CVE-2026-45942
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-45942

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

An ext4 allocation bitmap race can occur when the buddy bitmap fast path uses an uptodate folio by reference only while folio migration is in progress. A local workload that performs ext4 allocations under memory migration or huge page pressure can hit a narrow timing window and leave bitmap or group accounting state inconsistent. For the CVSS the PR:L is used because a local user with write access to the affected filesystem may trigger allocation activity, while full administrator privileges are not inherently required after the filesystem is mounted. The issue is not network reachable. Impact is mainly filesystem availability and integrity risk, including ext4 errors, possible filesystem shutdown, or inconsistent allocation metadata. Kernel memory corruption or privilege escalation is not directly indicated by this patch.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernel-0:6.12.0-211.61.1.el10_2Fixed 2026-09-28RHSA-2026:72624
Red Hat Enterprise Linux 8kernel-rt-0:4.18.0-553.169.1.rt7.510.el8_10Fixed 2026-09-28RHSA-2026:72467
Red Hat Enterprise Linux 8kernel-0:4.18.0-553.169.1.el8_10Fixed 2026-09-28RHSA-2026:72468
Red Hat Enterprise Linux 9kernel-0:5.14.0-687.53.1.el9_8Fixed 2026-09-28RHSA-2026:72623
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelAffected
Red Hat Enterprise Linux 7kernel-rtAffected
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-45942.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON