CyberRota Analysis
AI-GeneratedA vulnerability exists in the Linux kernel's handling of the itimerval structure, specifically on native sparc64 systems, where uninitialized padding in the structure can be exposed to userspace during the getitimer() call. This could potentially lead to information leakage, as the uninitialized memory may contain sensitive data. System administrators and developers working with Linux on sparc64 architecture should prioritize addressing this issue to mitigate the risk of unintended data exposure.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: timers/itimer: Zero-init old itimerval before copy to userspace On native sparc64, struct __kernel_old_timeval contains a four-byte hole after tv_usec because tv_sec is 64-bit while __kernel_suseconds_t is 32-bit. put_itimerval() fills only the named fields in a stack-allocated __kernel_old_itimerval and copies the entire object to userspace, so getitimer() can expose the two padding holes. Zero-initialize the aggregate before assigning the fields so implicit padding is deterministic before it crosses the user/kernel boundary.