CVE-2026-98935
What it is
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')
At a glance
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Received
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-98935.md and follow it. Check whether this project is affected by CVE-2026-98935. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://git.kernel.org/stable/c/00dc50cede96738dadc64b20e671186cddb8a58d
- https://git.kernel.org/stable/c/0ee5c5d804d592a8328a425b9274487d393d3a05
- https://git.kernel.org/stable/c/2838d7bbb551861c25187dfb581ed6e7a56762e9
- https://git.kernel.org/stable/c/a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb
- https://git.kernel.org/stable/c/beda3c9730ad3087d01aa1d0415c40942042ec87
- https://git.kernel.org/stable/c/f84eb9b7b0feeb267a174237d70a857042ce0158