GHSA-P9J5-GJF3-CCH6
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In 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')
{
"affected": [],
"aliases": [
"CVE-2026-98935"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:14Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nrtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak\n\nThe struct rtc_wkalrm has padding holes after the \u0027pending\u0027 member.\nWhen returned to userspace via the RTC_WKALRM_RD ioctl, uninitialized\nkernel stack data residing in these holes may be leaked.\n\nZero-initialize the struct at declaration to eliminate this information\nleak risk.\n\nFixes smatch warnings:\n- drivers/rtc/dev.c:392 rtc_dev_ioctl() warn: check that \u0027alarm\u0027 doesn\u0027t\n leak information (struct has a hole after \u0027pending\u0027)",
"id": "GHSA-p9j5-gjf3-cch6",
"modified": "2026-10-23T15:31:31Z",
"published": "2026-10-23T15:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98935"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/00dc50cede96738dadc64b20e671186cddb8a58d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0ee5c5d804d592a8328a425b9274487d393d3a05"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2838d7bbb551861c25187dfb581ed6e7a56762e9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a2215eb3cbbd3d9d73cc18c08e3ef53f903443cb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/beda3c9730ad3087d01aa1d0415c40942042ec87"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.