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.
Published: 2026-07-25
Score: 8.1 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

This flaw resides in the Linux kernel’s slab allocator memory‑zeroing logic. When the kernel is configured with only red zoning enabled, the zeroing routine incorrectly uses the full object size instead of the user‑requested allocation size, violating the __GFP_ZERO guarantee. As a result, residual data from previous allocations can be retained in the memory region and may be read by subsequent kernel operations, leading to information disclosure.

Affected Systems

Vendors: Linux kernel. All releases prior to the applied patch that compile with the SLAB_RED_ZONE configuration without SLAB_STORE_USER are affected. The flaw is independent of distribution or patch level; any kernel that has not been updated to the release containing the fix is vulnerable.

Risk and Exploitability

The CVSS score of 8.1 signals a high severity vulnerability. The EPSS score is reported as < 1 %, indicating a very low probability of current exploitation, and the vulnerability is not listed in the CISA KEV catalog. The vulnerability requires the kernel to be built with red zoning enabled and without user‑size tracking, which is a specific configuration. While an exploitation path is conceivable through privilege escalation or a local attacker gaining kernel memory allocation control, the attack vector is inferred rather than explicitly documented in the advisory. Overall risk remains low but non‑zero from a confidentiality perspective.

Generated by OpenCVE AI on August 3, 2026 at 19:01 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the slub_debug_orig_size() fix.
  • If a kernel update is not immediately available, rebuild the kernel disabling SLAB_RED_ZONE or enable SLAB_STORE_USER to enforce proper size tracking.
  • Verify the kernel build options to ensure that SLAB_RED_ZONE is not enabled alone and that the configuration matches the fix.

Generated by OpenCVE AI on August 3, 2026 at 19:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4724-1 linux-6.12 new package
History

Sun, 02 Aug 2026 13:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-206

Wed, 29 Jul 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-824
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 27 Jul 2026 06:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-206

Mon, 27 Jul 2026 05:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Sat, 25 Jul 2026 09:30:00 +0000

Type Values Removed Values Added
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.
Title mm/slab: do not limit zeroing to orig_size when only red zoning is enabled
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-05T12:41:09.726Z

Reserved: 2026-07-19T15:36:31.783Z

Link: CVE-2026-64368

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-07-25T10:17:19.613

Modified: 2026-08-11T15:01:50.637

Link: CVE-2026-64368

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-07-25T00:00:00Z

Links: CVE-2026-64368 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T19:15:04Z

Weaknesses
  • CWE-824

    Access of Uninitialized Pointer