CVE-2026-98847: Linux kernel · rtc: spear: initialize IRQ state before requesting alarm IRQ
Source GCVE Database
Not known to be exploited · fixed in e0cabda9b6f4dd276c55c40bdbb251e8507ae60e : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e0cabda9b6f4dd276c55c40bdbb251e8507ae60e, cb6d6a7fbff0414b9eed505d17687b4b7e38fee8, c02aa67ea34a826c2cb1aa65d77cf32fafb7eec3 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 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 has been applied to the Linux kernel to initialize the IRQ state before requesting the alarm IRQ. Users should update to the fixed kernel version once available. Since this is a kernel-level fix, applying the official kernel update is the recommended remediation.
Description
A vulnerability in the Linux kernel related to the RTC spear driver was resolved by initializing the IRQ state before requesting the alarm IRQ. The issue was that devm_request_irq() enables the interrupt before returning, potentially causing the interrupt handler to run while the device probe was still initializing. The fix involved initializing the MMIO address and spinlock prior to requesting the alarm IRQ.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98847 (opens in a new tab)
- git.kernel.org/stable/c/055ef5ce9f67a6a3a1363fa663007f8196cc0fb8 (opens in a new tab)
- git.kernel.org/stable/c/c02aa67ea34a826c2cb1aa65d77cf32fafb7eec3 (opens in a new tab)
- git.kernel.org/stable/c/cb6d6a7fbff0414b9eed505d17687b4b7e38fee8 (opens in a new tab)
- git.kernel.org/stable/c/e0cabda9b6f4dd276c55c40bdbb251e8507ae60e (opens in a new tab)
- git.kernel.org/stable/c/aeda50d645bbb55241be840602e338b3a16c24ca (opens in a new tab)