FKIE_CVE-2026-43067
Vulnerability from fkie_nvd - Published: 2026-05-05 16:16 - Updated: 2026-11-11 23:10| Vendor | Product | Version | |
|---|---|---|---|
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | 6.1.167 |
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/ext4/mballoc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "f89bba144938921a2249237ad04a0183ff3f8930",
"status": "affected",
"version": "9d89b9d55e25cb340c5b4b769876edc551b7a9ff",
"versionType": "git"
},
{
"lessThan": "83170a05908b6cf2fb3235d3065bf613ff866f3c",
"status": "affected",
"version": "1b0edd6022a3f44ce87fea9959a9310f4628fbea",
"versionType": "git"
},
{
"lessThan": "4bec4a498ce86314d470ae6144120461f2138c29",
"status": "affected",
"version": "9eea2f57d11b30049ff996ac3eff6e0dc8089e5f",
"versionType": "git"
},
{
"lessThan": "12624c5b724a81e14e532972b40d863b0de3b7d1",
"status": "affected",
"version": "34c803edc0b3365a42efcf9815acab63b4cf54e0",
"versionType": "git"
},
{
"lessThan": "2a368ccddfc492a0aa951e2caef2985f20e96503",
"status": "affected",
"version": "321ed8d559c951e71ad2d2d69a4cf0445644e865",
"versionType": "git"
},
{
"lessThan": "bb81702370fad22c06ca12b6e1648754dbc37e0f",
"status": "affected",
"version": "4865c768b563deff1b6a6384e74a62f143427b42",
"versionType": "git"
},
{
"status": "affected",
"version": "16fce6b6c0b247258c6c217fce5a48abf50f6964",
"versionType": "git"
},
{
"lessThan": "5.16",
"status": "affected",
"version": "5.15.203",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/ext4/mballoc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "6.1.168",
"status": "affected",
"version": "6.1.167",
"versionType": "semver"
},
{
"lessThan": "6.6.134",
"status": "affected",
"version": "6.6.130",
"versionType": "semver"
},
{
"lessThan": "6.12.80",
"status": "affected",
"version": "6.12.77",
"versionType": "semver"
},
{
"lessThan": "6.18.21",
"status": "affected",
"version": "6.18.14",
"versionType": "semver"
},
{
"lessThan": "6.19.11",
"status": "affected",
"version": "6.19.4",
"versionType": "semver"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "65BC3363-9FA5-4980-B120-042521BD0F34",
"versionEndExcluding": "5.16",
"versionStartIncluding": "5.15.203",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "B71F66A1-26CE-4A17-BBAB-34A1AE897567",
"versionEndExcluding": "6.6.134",
"versionStartIncluding": "6.6.130",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "C8D55175-C5FF-47BC-BC65-A2B06E3021A1",
"versionEndExcluding": "6.12.80",
"versionStartIncluding": "6.12.77",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "DEA57E4E-36B0-40D5-98B9-6A50348C9E74",
"versionEndExcluding": "6.18.21",
"versionStartIncluding": "6.18.14",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "A67B0458-DAE3-4940-BBB2-1A4D263AF27B",
"versionEndExcluding": "6.19.11",
"versionStartIncluding": "6.19.4",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:6.1.167:*:*:*:*:*:*:*",
"matchCriteriaId": "B898A4FB-4E74-40F7-B523-B71FFB681B6D",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: handle wraparound when searching for blocks for indirect mapped blocks\n\nCommit 4865c768b563 (\"ext4: always allocate blocks only from groups\ninode can use\") restricts what blocks will be allocated for indirect\nblock based files to block numbers that fit within 32-bit block\nnumbers.\n\nHowever, when using a review bot running on the latest Gemini LLM to\ncheck this commit when backporting into an LTS based kernel, it raised\nthis concern:\n\n If ac-\u003eac_g_ex.fe_group is \u003e= ngroups (for instance, if the goal\n group was populated via stream allocation from s_mb_last_groups),\n then start will be \u003e= ngroups.\n\n Does this allow allocating blocks beyond the 32-bit limit for\n indirect block mapped files? The commit message mentions that\n ext4_mb_scan_groups_linear() takes care to not select unsupported\n groups. However, its loop uses group = *start, and the very first\n iteration will call ext4_mb_scan_group() with this unsupported\n group because next_linear_group() is only called at the end of the\n iteration.\n\nAfter reviewing the code paths involved and considering the LLM\nreview, I determined that this can happen when there is a file system\nwhere some files/directories are extent-mapped and others are\nindirect-block mapped. To address this, add a safety clamp in\next4_mb_scan_groups()."
},
{
"lang": "es",
"value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta: ext4: manejar el desbordamiento al buscar bloques para bloques mapeados indirectamente El commit 4865c768b563 (\u2019ext4: siempre asignar bloques solo de grupos que el inodo puede usar\u2019) restringe qu\u00e9 bloques se asignar\u00e1n para archivos basados en bloques indirectos a n\u00fameros de bloque que encajen dentro de n\u00fameros de bloque de 32 bits. Sin embargo, al usar un bot de revisi\u00f3n ejecut\u00e1ndose en el \u00faltimo LLM Gemini para verificar este commit al hacer un backport a un kernel basado en LTS, plante\u00f3 esta preocupaci\u00f3n: \u2019Si ac -\u003e ac_g_ex.fe_group es mayor o igual que ngroups (por ejemplo, si el grupo objetivo fue poblado mediante asignaci\u00f3n de flujo desde s_mb_last_groups), entonces start ser\u00e1 mayor o igual que ngroups. \u00bfPermite esto asignar bloques m\u00e1s all\u00e1 del l\u00edmite de 32 bits para archivos mapeados por bloques indirectos? El mensaje del commit menciona que ext4_mb_scan_groups_linear() se encarga de no seleccionar grupos no soportados. Sin embargo, su bucle usa group = start, y la primera iteraci\u00f3n llamar\u00e1 a ext4_mb_scan_group() con este grupo no soportado porque next_linear_group() solo se llama al final de la iteraci\u00f3n.\u2019 Despu\u00e9s de revisar las rutas de c\u00f3digo involucradas y considerar la revisi\u00f3n del LLM, determin\u00e9 que esto puede ocurrir cuando hay un sistema de archivos donde algunos archivos/directorios est\u00e1n mapeados por extensiones y otros est\u00e1n mapeados por bloques indirectos. Para abordar esto, a\u00f1adir un l\u00edmite de seguridad en ext4_mb_scan_groups()."
}
],
"id": "CVE-2026-43067",
"lastModified": "2026-11-11T23:10:00.263",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-43067",
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-16T15:14:16.994971Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-05-05T16:16:15.937",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/12624c5b724a81e14e532972b40d863b0de3b7d1"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/2a368ccddfc492a0aa951e2caef2985f20e96503"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/4bec4a498ce86314d470ae6144120461f2138c29"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/83170a05908b6cf2fb3235d3065bf613ff866f3c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/bb81702370fad22c06ca12b6e1648754dbc37e0f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/f89bba144938921a2249237ad04a0183ff3f8930"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-822"
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.