A chained interrupt handler is registered during probe of the ts4800 driver but is never cleared when the driver is removed. The handler references memory that has already been freed, so when the parent interrupt fires after removal a dangling pointer is accessed and the kernel crashes. The Core Weakness is a use‑after‑free fault that can lead to denier of service by corrupting kernel memory and destabilizing the entire system. Based on the explanation, the likely attack vector is a local privilege escalation or user‑device interaction that triggers the parent interrupt after driver removal, though the CVE does not explicitly state whether remote exploitation is possible. The vulnerability does not provide a direct remote code execution path but can be abused to achieve a crash.

Affected systems are Linux kernel environments that include the ts4800 interrupt controller driver. The exact kernel versions are not listed, but any system that has compiled the ts4800 module and can load or unload it is potentially impacted. The driver is part of the generic Linux kernel, meaning many distributions and silicon platforms that use the ts4800 chipset are affected.

The risk level is moderate: the CVSS score of 5.5 indicates moderate severity. EPSS < 1% suggests a low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. The flaw allows a dangling chained handler to be invoked after the driver unloads, potentially causing a kernel crash and denial of service. Exploitation requires triggering the parent interrupt after the driver unloads, which may be achievable via local privilege escalation or by manipulating device events. No remote code execution path is documented, so the attack vector is likely local.