CVE-2026-98935: Linux kernel · rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in beda3c9730ad3087d01aa1d0415c40942042ec87 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:30 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in beda3c9730ad3087d01aa1d0415c40942042ec87, a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb, 2838d7bbb551861c25187dfb581ed6e7a56762e9 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel versions identified by the fixed commit hashes. Users should update to a kernel version that includes these fixes to prevent the information leak. No additional mitigation is required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's RTC device driver could leak uninitialized kernel stack data to userspace due to padding holes in the rtc_wkalrm structure. This occurs when the structure is returned via the RTC_WKALRM_RD ioctl call. The issue is resolved by zero-initializing the struct at declaration to prevent information leakage.
References
- git.kernel.org/stable/c/a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb (opens in a new tab)
- git.kernel.org/stable/c/beda3c9730ad3087d01aa1d0415c40942042ec87 (opens in a new tab)
- git.kernel.org/stable/c/00dc50cede96738dadc64b20e671186cddb8a58d (opens in a new tab)
- git.kernel.org/stable/c/2838d7bbb551861c25187dfb581ed6e7a56762e9 (opens in a new tab)
- git.kernel.org/stable/c/0ee5c5d804d592a8328a425b9274487d393d3a05 (opens in a new tab)