Affects Linux kernel ext4; edge-case could corrupt data or crash; widely deployed across servers and distros; high disruption risk.
CVE-2026-43067
Linux kernel ext4 32-bit block limit edge case may allow out-of-range allocations.
Is CVE-2026-43067 being exploited?
Not confirmed. CVE-2026-43067 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-43067?
CVE-2026-43067 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-43067?
Yes. A fix has been recorded for CVE-2026-43067. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-43067 affect?
CVE-2026-43067 affects Linux kernel, ext4 filesystem. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-43067?
Upgrade to patched kernel or backport fix to LTS
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Block allocation may exceed 32-bit limit for indirect blocks, risking data corruption or kernel panic.
Patch when possible
- affected>= 9d89b9d55e25cb340c5b4b769876edc551b7a9ff and < f89bba144938921a2249237ad04a0183ff3f8930
- affected>= 1b0edd6022a3f44ce87fea9959a9310f4628fbea and < 83170a05908b6cf2fb3235d3065bf613ff866f3c
- affected>= 9eea2f57d11b30049ff996ac3eff6e0dc8089e5f and < 4bec4a498ce86314d470ae6144120461f2138c29
- affected>= 34c803edc0b3365a42efcf9815acab63b4cf54e0 and < 12624c5b724a81e14e532972b40d863b0de3b7d1
- affected>= 321ed8d559c951e71ad2d2d69a4cf0445644e865 and < 2a368ccddfc492a0aa951e2caef2985f20e96503
- affected>= 4865c768b563deff1b6a6384e74a62f143427b42 and < bb81702370fad22c06ca12b6e1648754dbc37e0f
- affected16fce6b6c0b247258c6c217fce5a48abf50f6964
- affected>= 5.15.203 and < 5.16
- affected>= 6.1.167 and < 6.1.168
- affected>= 6.6.130 and < 6.6.134
- affected>= 6.12.77 and < 6.12.80
- affected>= 6.18.14 and < 6.18.21
- affected>= 6.19.4 and < 6.19.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.