Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43067ext4: handle wraparound when searching for blocks for indirect mapped blocks

Description

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().

Timeline

  1. ID reserved

    By Linux

  2. · 4 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43067, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.50% · top 56% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 9d89b9d55e25cb340c5b4b769876edc551b7a9ff – < f89bba144938921a2249237ad04a0183ff3f8930
    • affected 1b0edd6022a3f44ce87fea9959a9310f4628fbea – < 83170a05908b6cf2fb3235d3065bf613ff866f3c
    • affected 9eea2f57d11b30049ff996ac3eff6e0dc8089e5f – < 4bec4a498ce86314d470ae6144120461f2138c29
    • affected 34c803edc0b3365a42efcf9815acab63b4cf54e0 – < 12624c5b724a81e14e532972b40d863b0de3b7d1
    • affected 321ed8d559c951e71ad2d2d69a4cf0445644e865 – < 2a368ccddfc492a0aa951e2caef2985f20e96503
    • affected 4865c768b563deff1b6a6384e74a62f143427b42 – < bb81702370fad22c06ca12b6e1648754dbc37e0f
    • affected 16fce6b6c0b247258c6c217fce5a48abf50f6964
    • affected 5.15.203 – < 5.16
  • Linux · Linux

    • affected 6.1.167 – < 6.1.168
    • affected 6.6.130 – < 6.6.134
    • affected 6.12.77 – < 6.12.80
    • affected 6.18.14 – < 6.18.21
    • affected 6.19.4 – < 6.19.11

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43067 badge
[![CVE-2026-43067](https://cveledger.app/badge/CVE-2026-43067.svg)](https://cveledger.app/cve/CVE-2026-43067)

Record last updated .