CVE-2026-64368: mm/slab: do not limit zeroing to orig_size when only red zoning is enabled
Vulnerability summary
CVE-2026-64368 is a high (CVSS 8.1) Improper Initialization vulnerability in linux. EPSS estimates a 0.42% chance of exploitation in the next 30 days, higher than 36% of scored vulnerabilities.
Severe, CVSS 8.1 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 0% (FIRST, 03-11-2026)
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 25 · Related 20Timeline
- 25-07-2026PublishedVulnerability first disclosed.
- 19-10-2026Last modifiedVulnerability information updated.
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.
CVSS metrics
4 scores · 4 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated8.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- OSV · DebianEcosystem advisory · calculated8.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- NVDNIST8.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS trend
Probability
0.42%
Chance of exploitation in the next 30 days
Percentile
36%
Versus all other CVEs
30-day change
No change 0.00 pp
From 0.42% on 04-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeAffected systems
Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu142 products
- linuxAll versions (No fix recorded) | < 6.8.0-147.147 | < 7.0.0-31.31
- linux-allwinner-5.19All versions (No fix recorded)
- linux-awsAll versions (No fix recorded) | < 6.8.0-1067.70 | < 7.0.0-1012.12
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Debian2 products
- linux< 6.12.96-1 | < 7.1.4-1
- linux-6.12< 6.12.100-1~deb12u1
Linux2 products
- linux≥ 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, < 6256899c3a34674bba6076884aedbba49fc695e4 | ≥ 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, < 7e706d50fa119eead6376bf0ef973e8d73a96030 | ≥ 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, < 2382971aaaef5bf85a651234c64906f59580b8be | ≥ 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, < 0d18ccef142f04433dfb2a0c120cf223d2b8a42c | ≥ 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, < 648927ceb84021a25a0fbd5673740956f318d534 | 6.2
- linux_kernel≥ 6.2, < 6.6.145 | ≥ 6.7, < 6.12.96 | ≥ 6.13, < 6.18.39 | ≥ 6.19, < 7.1.4
3 vendors · 146 products