cve.bz

CVE-2026-43067 linux linux kernel: Untrusted Pointer Dereference

9.8 criticalEPSS 0.5%Fix available

Critical (9.8) in linux linux kernel. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: ext4: handle wraparound when searching for blocks for indirect mapped blocks Commit 4865c768b563 ("ext4: always allocate blocks only from groups inode can use") restricts what blocks will be allocated for indirect block based files to block numbers that fit within 32-bit block numbers. However, when using a review bot running on the latest Gemini LLM to check this commit when backporting into an LTS based kernel, it raised this concern: If ac->ac_g_ex.fe_group is >= ngroups (for instance, if the goal group was populated via stream allocation from s_mb_last_groups), then start will be >= ngroups. Does this allow allocating blocks beyond the 32-bit limit for indirect block mapped files? The commit message mentions that ext4_mb_scan_groups_linear() takes care to not select unsupported groups. However, its loop uses group = *start, and the very first iteration will call ext4_mb_scan_group() with this unsupported group because next_linear_group() is only called at the end of the iteration. After reviewing the code paths involved and considering the LLM review, I determined that this can happen when there is a file system where some files/directories are extent-mapped and others are indirect-block mapped. To address this, add a safety clamp in ext4_mb_scan_groups().

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th 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: yes · 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-822 Untrusted Pointer Dereference
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-43067 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-43067?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-43067?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-43067 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
Linuxfrom 5.15.203 before 5.16
Linuxfrom 6.1.167 before 6.1.168
Linuxfrom 6.6.130 before 6.6.134
Linuxfrom 6.12.77 before 6.12.80
Linuxfrom 6.18.14 before 6.18.21
Linuxfrom 6.19.4 before 6.19.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux6.19.11-1DEBIAN-CVE-2026-43067
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-43067
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-43067
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-43067
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 47 moreno fix listedUBUNTU-CVE-2026-43067
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 13 moreno fix listedUBUNTU-CVE-2026-43067
UbuntuNvidia-BlueField:22.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-43067
UbuntuPro:20.04:LTSlinux-aws-5.15, linux-gcp-5.15, linux-hwe-5.15 and 8 moreno fix listedUBUNTU-CVE-2026-43067
UbuntuPro:FIPS-updates:22.04:LTSlinux-fips, linux-aws-fips, linux-gcp-fips and 1 moreno fix listedUBUNTU-CVE-2026-43067
UbuntuPro:Realtime:22.04:LTSlinux-realtime, linux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-43067
UbuntuPro:Realtime:24.04:LTSlinux-realtime-6.14no fix listedUBUNTU-CVE-2026-43067
Alpaquita23linux-lts6.1.168-r0BELL-CVE-2026-43067
Alpaquita25linux-lts6.12.80-r0BELL-CVE-2026-43067
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-43067

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelOut of support scope
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelFix deferred
Red Hat Enterprise Linux 7kernel-rtFix deferred
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtOut of support scope
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtOut of support scope

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-43067.

Attack patterns (CAPEC)

  • CAPEC-129 Pointer Manipulation Severity: Medium

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

References

Check your stackJSON