vfio/fsl-mc: Block calling interrupt handler without trigger
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cc0ee20bd96971c10eba9a83ecf1c0733078a083 · < 6ec0d88166dac43f29e96801c0927d514f17add9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vfio/fsl-mc: Block calling interrupt handler without trigger
The eventfd_ctx trigger pointer of the vfio_fsl_mc_irq object is initially NULL and may become NULL if the user sets the trigger eventfd to -1. The interrupt handler itself is guaranteed that trigger is always valid between request_irq() and free_irq(), but the loopback testing mechanisms to invoke the handler function need to test the trigger. The triggering and setting ioctl paths both make use of igate and are therefore mutually exclusive.
The vfio-fsl-mc driver does not make use of irqfds, nor does it support any sort of masking operations, therefore unlike vfio-pci and vfio-platform, the flow can remain essentially unchanged.
From the CVE record · Linux
The vfio/fsl-mc interrupt handler can be invoked through a loopback testing path when its eventfd trigger pointer is NULL. A user can set the trigger eventfd to -1 and invoke the handler through that path, potentially causing a NULL pointer dereference. The input does not specify whether authentication or other user interaction is required.
Engineers running Linux kernels with the vfio/fsl-mc driver should check their systems; affected versions are not specified.