vfio/pci: Lock external INTx masking ops
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 · < 6fe478d855b20ac1eb5da724afe16af5a2aaaa40| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vfio/pci: Lock external INTx masking ops
Mask operations through config space changes to DisINTx may race INTx configuration changes via ioctl. Create wrappers that add locking for paths outside of the core interrupt code.
In particular, irq_type is updated holding igate, therefore testing is_intx() requires holding igate. For example clearing DisINTx from config space can otherwise race changes of the interrupt configuration.
This aligns interfaces which may trigger the INTx eventfd into two camps, one side serialized by igate and the other only enabled while INTx is configured. A subsequent patch introduces synchronization for the latter flows.
From the CVE record · Linux
The Linux kernel's vfio/pci INTx masking operations can race with interrupt configuration changes via ioctl. The race can occur when DisINTx is changed through config space while interrupt configuration is changing; the input does not specify attacker access requirements or a resulting exploit impact.
Teams running Linux kernels with vfio/pci should check their versions against the vendor advisory; affected versions are not specified.