CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's memory allocation functions, specifically the kmalloc() and krealloc() operations, which improperly handle memory zeroing when red zoning is enabled without tracking the requested size. This flaw can lead to potential data leakage, as it may expose uninitialized memory contents, compromising the integrity of sensitive information. Organizations utilizing Linux systems, especially those with high-security requirements, should prioritize addressing this vulnerability to mitigate risks associated with memory management.
Original NVD 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.