CVE-2026-98935: rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 00dc50cede96738dadc64b20e671186cddb8a58d, 0ee5c5d804d592a8328a425b9274487d393d3a05, 2838d7bbb551861c25187dfb581ed6e7a56762e9; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 00dc50cede96738dadc64b20e671186cddb8a58d, 0ee5c5d804d592a8328a425b9274487d393d3a05, 2838d7bbb551861c25187dfb581ed6e7a56762e9; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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')
- Published
- Oct 23, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.0affected
- 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 and later · before f84eb9b7b0feeb267a174237d70a857042ce0158affected · git
- 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 and later · before a2215eb3cbbd3d9d73cc18c08e3ef53f903443cbaffected · git
- 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 and later · before beda3c9730ad3087d01aa1d0415c40942042ec87affected · git
- 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 and later · before 00dc50cede96738dadc64b20e671186cddb8a58daffected · git
- 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 and later · before 2838d7bbb551861c25187dfb581ed6e7a56762e9affected · git
- 36e14f5fdfdf7cec8887b7ff69cd9bb5051ecf62 and later · before 0ee5c5d804d592a8328a425b9274487d393d3a05affected · git
- before 5.0not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98933Oct 23, 2026 · usb: hub: use shorter 120ms post resume hold for SS root hubs0Monitor
- ← EarlierCVE-2026-98934Oct 23, 2026 · ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()0Monitor
- Later →CVE-2026-98936Oct 23, 2026 · wifi: ath11k: reset ar->num_stations on hardware start0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 00dc50cede96738dadc64b20e671186cddb8a58d | Vendor (CNA) |
| Linux Linux | 0ee5c5d804d592a8328a425b9274487d393d3a05 | Vendor (CNA) |
| Linux Linux | 2838d7bbb551861c25187dfb581ed6e7a56762e9 | Vendor (CNA) |
| Linux Linux | a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb | Vendor (CNA) |
| Linux Linux | beda3c9730ad3087d01aa1d0415c40942042ec87 | Vendor (CNA) |
| Linux Linux | f84eb9b7b0feeb267a174237d70a857042ce0158 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 3, 2026+10 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1390 · Oct 26, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/0ee5c5d804d592a8328a425b9274487d393d3a05
- git.kernel.org/stable/c/2838d7bbb551861c25187dfb581ed6e7a56762e9
- git.kernel.org/stable/c/a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb
- git.kernel.org/stable/c/beda3c9730ad3087d01aa1d0415c40942042ec87
- git.kernel.org/stable/c/f84eb9b7b0feeb267a174237d70a857042ce0158
Vendor advisories and official records. Exploit/PoC links are deliberately left out.