CVE-2026-64368mm/slab: do not limit zeroing to orig_size when only red zoning is enabled
- 8.1HighCVSS base score
- 0.42%Exploitation in 30 daysEPSS · top 63% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: mm/slab: do not limit zeroing to orig_size when only red zoning is enabled When init (zeroing) on allocation is requested, for kmalloc() we generally have to zero the full object size even if a smaller size is requested, in order to provide krealloc()'s __GFP_ZERO guarantees. But if we track the requested size, krealloc() uses that information to do the right thing, so we can zero only the requested size. With red zoning also enabled, any extra size became part of the red zone, so it must not be zeroed and thus we must zero only the requested size. However the current check is imprecise, and will trigger also when only SLAB_RED_ZONE is enabled without SLAB_STORE_USER (which enables tracking the requested size). This means enabling red zoning alone can compromise krealloc()'s __GFP_ZERO contract. Fix this by using slub_debug_orig_size() instead, which is the exact check for whether the requested size is tracked. We don't need to care if red zoning is also enabled or not. Also update and expand the comment accordingly.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.42% · top 63% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.
Affected products
- affected 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 – < 6256899c3a34674bba6076884aedbba49fc695e4
- affected 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 – < 7e706d50fa119eead6376bf0ef973e8d73a96030
- affected 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 – < 2382971aaaef5bf85a651234c64906f59580b8be
- affected 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 – < 0d18ccef142f04433dfb2a0c120cf223d2b8a42c
- affected 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 – < 648927ceb84021a25a0fbd5673740956f318d534
- affected 6.2
- unaffected < 6.2
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/6256899c3a34674bba6076884aedbba49fc695e4 (opens in a new tab)
- https://git.kernel.org/stable/c/7e706d50fa119eead6376bf0ef973e8d73a96030 (opens in a new tab)
- https://git.kernel.org/stable/c/2382971aaaef5bf85a651234c64906f59580b8be (opens in a new tab)
- https://git.kernel.org/stable/c/0d18ccef142f04433dfb2a0c120cf223d2b8a42c (opens in a new tab)
- https://git.kernel.org/stable/c/648927ceb84021a25a0fbd5673740956f318d534 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48912 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64368)Record last updated .