rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.113, 6.18.56, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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')
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 · fixed in a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb; From 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 · fixed in beda3c9730ad3087d01aa1d0415c40942042ec87; From 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 · fixed in 00dc50cede96738dadc64b20e671186cddb8a58d; From 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 · fixed in 2838d7bbb551861c25187dfb581ed6e7a56762e9; From 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 · fixed in 0ee5c5d804d592a8328a425b9274487d393d3a05
- Linux Linux
5.0
- KernelLinux
From 5.0.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10