Impact
During initialization of the msc313 RTC driver, a shared IRQ is requested before driver data is bound to the device. If another device sharing the IRQ triggers the handler while the data pointer is still NULL, the handler dereferences a NULL pointer in interrupt context, causing a kernel panic. This null pointer dereference (CWE‑476) results in a denial‑of‑service event.
Affected Systems
Any Linux kernel that includes the unpatched msc313 RTC driver is affected. The advisory does not list specific versions, so all releases containing the described probe sequence are potentially impacted unless the commit that passes the private data directly as the IRQ cookie has been applied.
Risk and Exploitability
The CVSS score of 5.5 signals a medium severity vulnerability, and the EPSS score of < 1% indicates a low probability of exploitation under normal circumstances. The flaw is exploitable only when another device shares the same IRQ line and can trigger it while the driver is in the vulnerable window, making it a local‑only attack vector. It is not listed in the CISA KEV catalog and thus has no known active exploit code, but a kernel panic can still be forced by a malicious or misbehaving peripheral in embedded or tightly coupled environments.
OpenCVE Enrichment