Answer in brief
CVE-2026-64368 records a Unknown severity vulnerability in mm/slab: do not limit zeroing to orig_size when only red zoning is enabled. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <6256899c3a34674bba6076884aedbba49fc695e4 || >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <7e706d50fa119eead6376bf0ef973e8d73a96030 || >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <2382971aaaef5bf85a651234c64906f59580b8be || >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <0d18ccef142f04433dfb2a0c120cf223d2b8a42c || >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <648927ceb84021a25a0fbd5673740956f318d534 | 6256899c3a34674bba6076884aedbba49fc695e4, 7e706d50fa119eead6376bf0ef973e8d73a96030, 2382971aaaef5bf85a651234c64906f59580b8be, 0d18ccef142f04433dfb2a0c120cf223d2b8a42c, 648927ceb84021a25a0fbd5673740956f318d534 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64368 records a Unknown severity vulnerability in mm/slab: do not limit zeroing to orig_size when only red zoning is enabled. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <6256899c3a34674bba6076884aedbba49fc695e4 || >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <7e706d50fa119eead6376bf0ef973e8d73a96030 || >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <2382971aaaef5bf85a651234c64906f59580b8be || >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <0d18ccef142f04433dfb2a0c120cf223d2b8a42c || >=9ce67395f5a0cdec6ce152d26bfda13b98b25c01 <648927ceb84021a25a0fbd5673740956f318d534 | 6256899c3a34674bba6076884aedbba49fc695e4, 7e706d50fa119eead6376bf0ef973e8d73a96030, 2382971aaaef5bf85a651234c64906f59580b8be, 0d18ccef142f04433dfb2a0c120cf223d2b8a42c, 648927ceb84021a25a0fbd5673740956f318d534 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.