ASoC: sti: initialize IRQ lock before requesting IRQ
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 · < 998ca92f69bc43499705016d02ffaf0663126d57| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ASoC: sti: initialize IRQ lock before requesting IRQ
uni_reader_init() registers the shared IRQ before initializing reader->irq_lock. 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.
From the CVE record · Linux
The Linux kernel’s ASoC sti uni_reader_init() registers a shared IRQ before initializing its lock. A pending interrupt during that window can invoke the handler with an uninitialized lock; the input does not describe an attacker action or specify network access, authentication, or user interaction.
Engineers running Linux kernels with the ASoC sti driver should check whether their kernel includes the fix; affected versions are not specified.