CVE-2026-64368
Received Received - Intake

BaseFortify

Vulnerability report for CVE-2026-64368, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-25

Last updated on: 2026-07-25

Assigner: kernel.org

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-25
Last Modified
2026-07-25
Generated
2026-07-25
AI Q&A
2026-07-25
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves incorrect zeroing behavior during memory allocation when red zoning is enabled. Normally, krealloc() requires full object zeroing for __GFP_ZERO guarantees, but the current check incorrectly limits zeroing to the requested size even when only red zoning is enabled without tracking the original size. This breaks the expected behavior of krealloc() when red zoning is used alone.

Detection Guidance

This vulnerability is specific to the Linux kernel's memory management (SLAB allocator) and does not have network-based detection methods. Detection involves checking kernel configuration and behavior related to SLAB_RED_ZONE and krealloc() usage. Review kernel logs for slab-related errors or unexpected behavior during memory allocation.

Impact Analysis

This vulnerability could lead to memory corruption or unexpected behavior in applications relying on krealloc() with __GFP_ZERO. If red zoning is enabled without SLAB_STORE_USER, the kernel may not zero the full allocated memory, potentially exposing sensitive data or causing crashes in affected systems.

Mitigation Strategies

Apply the kernel patch that fixes the SLAB_RED_ZONE and krealloc() zeroing issue. Update to a Linux kernel version that includes the fix. If immediate patching is not possible, disable SLAB_RED_ZONE in kernel configuration to prevent the incorrect zeroing behavior.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64368. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart