In the Linux kernel, the following vulnerability has been resolved:
dmaengine: fsl-qdma: init irq after reg initialization
Initialize the qDMA irqs after the registers are configured so that interrupts that may have been pending from a primary kernel don't get processed by the irq handler before it is ready to and cause panic with the following trace:
Call trace: fslqdmaqueuehandler+0xf8/0x3e8 _handleirqeventpercpu+0x78/0x2b0 handleirqeventpercpu+0x1c/0x68 handleirqevent+0x44/0x78 handlefasteoiirq+0xc8/0x178 generichandleirq+0x24/0x38 _handledomainirq+0x90/0x100 gichandleirq+0x5c/0xb8 el1irq+0xb8/0x180 rawspinunlockirqrestore+0x14/0x40 _setupirq+0x4bc/0x798 requestthreadedirq+0xd8/0x190 devmrequestthreadedirq+0x74/0xe8 fslqdmaprobe+0x4d4/0xca8 platformdrvprobe+0x50/0xa0 reallyprobe+0xe0/0x3f8 driverprobedevice+0x64/0x130 devicedriverattach+0x6c/0x78 _driverattach+0xbc/0x158 busforeachdev+0x5c/0x98 driverattach+0x20/0x28 busadddriver+0x158/0x220 driverregister+0x60/0x110 _platformdriverregister+0x44/0x50 fslqdmadriverinit+0x18/0x20 dooneinitcall+0x48/0x258 kernelinitfreeable+0x1a4/0x23c kernelinit+0x10/0xf8 retfromfork+0x10/0x18