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… (CVE-2026-64368)
A vulnerability in the Linux kernel's memory management slab allocator was resolved. The issue involved incorrect zeroing behavior when only red zoning was enabled without tracking the requested allocation size. This could compromise the guarantees of krealloc() with __GFP_ZERO flag. The fix involves a more precise check to ensure zeroing is done correctly based on tracked requested size.
AI Analysis
Technical Summary
The Linux kernel's slab allocator had a flaw where enabling only SLAB_RED_ZONE without SLAB_STORE_USER caused improper zeroing of allocated memory. Normally, when zeroing is requested, the entire object size is zeroed to meet krealloc()'s __GFP_ZERO guarantees. However, with red zoning enabled alone, the code incorrectly zeroed the entire object size instead of just the requested size, potentially violating the zeroing contract. The vulnerability was fixed by using slub_debug_orig_size() to accurately determine if the requested size is tracked, ensuring correct zeroing behavior regardless of red zoning status.
Potential Impact
This vulnerability could lead to scenarios where memory zeroing guarantees provided by krealloc() with __GFP_ZERO are not met, potentially exposing uninitialized memory contents. However, no known exploits in the wild have been reported. The impact is limited to kernel memory management behavior and may affect kernel stability or security depending on usage.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source to address this issue. Users should apply the official kernel updates that include this patch. Since this is a kernel-level vulnerability, updating to a fixed kernel version is the recommended remediation. Patch status is not explicitly confirmed here; users should consult the Linux kernel vendor advisory or distribution security updates for the exact fixed versions and apply them accordingly.
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… (CVE-2026-64368)
Description
A vulnerability in the Linux kernel's memory management slab allocator was resolved. The issue involved incorrect zeroing behavior when only red zoning was enabled without tracking the requested allocation size. This could compromise the guarantees of krealloc() with __GFP_ZERO flag. The fix involves a more precise check to ensure zeroing is done correctly based on tracked requested size.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's slab allocator had a flaw where enabling only SLAB_RED_ZONE without SLAB_STORE_USER caused improper zeroing of allocated memory. Normally, when zeroing is requested, the entire object size is zeroed to meet krealloc()'s __GFP_ZERO guarantees. However, with red zoning enabled alone, the code incorrectly zeroed the entire object size instead of just the requested size, potentially violating the zeroing contract. The vulnerability was fixed by using slub_debug_orig_size() to accurately determine if the requested size is tracked, ensuring correct zeroing behavior regardless of red zoning status.
Potential Impact
This vulnerability could lead to scenarios where memory zeroing guarantees provided by krealloc() with __GFP_ZERO are not met, potentially exposing uninitialized memory contents. However, no known exploits in the wild have been reported. The impact is limited to kernel memory management behavior and may affect kernel stability or security depending on usage.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source to address this issue. Users should apply the official kernel updates that include this patch. Since this is a kernel-level vulnerability, updating to a fixed kernel version is the recommended remediation. Patch status is not explicitly confirmed here; users should consult the Linux kernel vendor advisory or distribution security updates for the exact fixed versions and apply them accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m4hc-cp9r-f6rj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64368"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420b9c2644c7f808473d
Added to database: 07/25/2026, 23:08:59 UTC
Last enriched: 07/25/2026, 23:28:31 UTC
Last updated: 07/26/2026, 06:23:41 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.