Bug 2532295 (CVE-2026-89765) - CVE-2026-89765 kernel: Kernel: Information disclosure in timers/itimer due to uninitialized padding
Summary: CVE-2026-89765 kernel: Kernel: Information disclosure in timers/itimer due to...
Keywords:
Status: NEW
Alias: CVE-2026-89765
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-11 22:11 UTC by OSIDB Bzimport
Modified: 2026-09-11 22:23 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-11 22:11:34 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.