CVE-2026-97909: ASoC: sti: initialize IRQ lock before requesting IRQ
In the Linux kernel, the following vulnerability has been resolved:
ASoC: sti: initialize IRQ lock before requesting IRQ
unireaderinit() registers the shared IRQ before initializing reader->irqlock. A pending interrupt can invoke the handler while the lock is still uninitialized.
Initialize the lock before registering the IRQ so the interrupt path always sees valid lock state.
Affected Software
Event History
Frequently Asked Questions
What systems are exposed to this issue?
Systems using the Linux kernel's ASoC STI uni_reader initialization path are exposed when that code registers its shared IRQ before initializing the associated IRQ lock.
What must occur for the vulnerability to be triggered?
A pending interrupt must be delivered after the shared IRQ is registered but before reader->irq_lock has been initialized. The interrupt handler can then access an uninitialized lock state.
Is this dependent on an external attacker being able to send a request?
The provided information describes a local kernel initialization race involving a pending hardware interrupt. It does not state that exploitation requires a network request or any particular external attacker capability.
What is the remediation?
Apply a kernel update containing the fix that initializes reader->irq_lock before registering the shared IRQ. This ensures the interrupt handler always observes a valid lock state.