crypto: keembay - Initialize completion before requesting IRQ
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 88574332451380f4b51f6ca88ab9810e714bfb9b · < 5aae80dcec0748b4ed61daace2ad8b12082261f2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: keembay - Initialize completion before requesting IRQ
kmb_ocs_aes_probe() requests the device IRQ before initializing irq_completion. Once the handler is registered it can run immediately, and ocs_aes_irq_handler() unconditionally calls complete(). An interrupt in this window would therefore use an uninitialized completion.
Initialize the completion before requesting the IRQ, as the sibling OCS HCU and ECC drivers already do.
From the CVE record · Linux
The Linux kernel’s keembay crypto driver requests an IRQ before initializing a completion object. If an interrupt arrives in that window, its handler uses the uninitialized object; the input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the keembay crypto driver should check their versions; affected versions are not specified.