Skip to main content
VulnerabilityPublished

CVE-2026-98935: Linux kernel · rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak

Source GCVE Database

0
Authoritative record:CVE-2026-98935

Not known to be exploited · fixed in beda3c9730ad3087d01aa1d0415c40942042ec87 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · 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

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62, < beda3c9730ad3087d01aa1d0415c40942042ec87
Fixed in
  • beda3c9730ad3087d01aa1d0415c40942042ec87
LinuxLinuxAffected
  • ≥ 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62, < a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb
Fixed in
  • a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb
LinuxLinuxAffected
  • ≥ 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62, < 2838d7bbb551861c25187dfb581ed6e7a56762e9
Fixed in
  • 2838d7bbb551861c25187dfb581ed6e7a56762e9
LinuxLinuxAffected
  • ≥ 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62, < 0ee5c5d804d592a8328a425b9274487d393d3a05
Fixed in
  • 0ee5c5d804d592a8328a425b9274487d393d3a05
LinuxLinuxAffected
  • ≥ 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62, < 00dc50cede96738dadc64b20e671186cddb8a58d
Fixed in
  • 00dc50cede96738dadc64b20e671186cddb8a58d
LinuxLinuxAffected
  • =5.0
Fixed in–

Description

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')

References

Community reviews

Loading reviews…