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: Information Disclosure
Action: Patch Kernel
AI Analysis

Impact

The flaw resides in the slab allocation logic of the Linux kernel. When an allocation request includes the __GFP_ZERO flag, the kernel is required to zero the entire object size. If only SLAB_RED_ZONE is enabled and SLAB_STORE_USER is disabled, the current check mistakenly stops zeroing after the requested size and leaves the red‑zone portion uncleared. This means the integrity of the __GFP_ZERO contract is violated, potentially exposing stale kernel memory to subsequent uses.

Affected Systems

Linux kernels compiled with SLAB_RED_ZONE enabled and SLAB_STORE_USER disabled are impacted. Any build that lacks the upstream patch that replaces the imprecise check with slub_debug_orig_size() is vulnerable. Version information is not specified, so the exact range of affected kernel releases is unknown.

Risk and Exploitability

The CVSS score of 8.1 classifies the vulnerability as high severity. The EPSS score is less than 1%, indicating a low likelihood of current exploitation. It is not listed in the CISA KEV catalog. Exploitation requires a kernel configuration that matches the vulnerable state and local control over the allocator; under typical use the risk of active attack remains low.

Generated by OpenCVE AI on October 23, 2026 at 00:11 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the system to a Linux kernel release that contains the slub_debug_orig_size() fix.
  • If a kernel update cannot be performed immediately, rebuild the kernel with SLAB_RED_ZONE disabled or enable SLAB_STORE_USER so that size tracking is correctly performed.
  • Verify kernel configuration and rebuild any custom kernels or modules to avoid the vulnerable combination of SLAB_RED_ZONE without SLAB_STORE_USER.

Generated by OpenCVE AI on October 23, 2026 at 00:11 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
Ubuntu USN Ubuntu USN USN-8726-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8727-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-2 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-3 Linux kernel (IBM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8800-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-2 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-4 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
Ubuntu USN Ubuntu USN USN-8917-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8918-1 Linux kernel (Azure) vulnerabilities
History

Mon, 19 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Fri, 16 Oct 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 04 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo

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-10-19T20:38:24.997Z

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

Link: CVE-2026-64368

cve-icon Vulnrichment

Updated: 2026-10-16T15:39:32.373Z

cve-icon NVD

Status : Modified

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

Modified: 2026-10-19T21:17:33.260

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-10-23T00:15:13Z

Weaknesses