Answer in brief
CVE-2026-98935 records a Unknown severity vulnerability in rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 <a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb || >=36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 <beda3c9730ad3087d01aa1d0415c40942042ec87 || >=36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 <00dc50cede96738dadc64b20e671186cddb8a58d || >=36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 <2838d7bbb551861c25187dfb581ed6e7a56762e9 || >=36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 <0ee5c5d804d592a8328a425b9274487d393d3a05 | a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb, beda3c9730ad3087d01aa1d0415c40942042ec87, 00dc50cede96738dadc64b20e671186cddb8a58d, 2838d7bbb551861c25187dfb581ed6e7a56762e9, 0ee5c5d804d592a8328a425b9274487d393d3a05 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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')
Quoted source text, attributed separately from HOL analysis.