Live › vulnerability › CVE-2026-98847
Go to dashboardIn the Linux kernel's SPEAr real-time clock driver, the alarm interrupt was requested before the device's register address and spinlock were set up, so the handler could run during probe while that state was still uninitialized. The sources do not describe an attacker-controlled trigger or a concrete impact beyond this ordering bug.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the SPEAr RTC driver (rtc-spear) built in or loaded, which is mainly ARM SPEAr-based embedded boards. The sources do not say who can skip it beyond that, and the description gives no evidence of remote reach.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
rtc: spear: initialize IRQ state before requesting alarm IRQ
devm_request_irq() enables the interrupt before it returns, so the handler may run while probe is still initializing the device. Initialize the MMIO address and spinlock before requesting the alarm IRQ.
This page as .md · .json · in your agent: get_signal("CVE-2026-98847")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.