Linux kernel stack data exposure in RTC alarm ioctl
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 · < 0ee5c5d804d592a8328a425b9274487d393d3a05| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak
The struct rtc_wkalrm has padding holes after the 'pending' member. When returned to userspace via the RTC_WKALRM_RD ioctl, uninitialized kernel stack data residing in these holes may be leaked.
Zero-initialize the struct at declaration to eliminate this information leak risk.
Fixes smatch warnings: - drivers/rtc/dev.c:392 rtc_dev_ioctl() warn: check that 'alarm' doesn't leak information (struct has a hole after 'pending')
From the CVE record · Linux
The Linux kernel’s RTC_WKALRM_RD ioctl can return uninitialized kernel stack data from padding in struct rtc_wkalrm. A local user able to call the ioctl may receive that data; the input does not specify authentication requirements.
Engineers running Linux kernels with the affected RTC device code should check their systems; affected versions are not specified.