NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e75d5ae8ab88b7ffb3d1d56124b003f3555f74b4 · < d876153680e3d721d385e554def919bce3d18c74| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR
When BAR_PEER_SPAD and BAR_CONFIG share one PCI BAR, the module teardown path ends up calling pci_iounmap() on the same iomem with some offset, which is unnecessary and triggers a kernel warning like the following:
Trying to vunmap() nonexistent vm area (0000000069a5ffe8) WARNING: mm/vmalloc.c:3470 at vunmap+0x58/0x68, CPU#5: modprobe/2937 [...] Call trace: vunmap+0x58/0x68 (P) iounmap+0x34/0x48 pci_iounmap+0x2c/0x40 ntb_epf_pci_remove+0x44/0x80 [ntb_hw_epf] pci_device_remove+0x48/0xf8 device_remove+0x50/0x88 device_release_driver_internal+0x1c8/0x228 driver_detach+0x50/0xb0 bus_remove_driver+0x74/0x100 driver_unregister+0x34/0x68 pci_unregister_driver+0x34/0xa0 ntb_epf_pci_driver_exit+0x14/0xfe0 [ntb_hw_epf] [...]
Fix it by unmapping only when PEER_SPAD and CONFIG use difference bars.
From the CVE record · Linux
The Linux kernel NTB EPF driver can call pci_iounmap() with an offset during module teardown when PEER_SPAD and CONFIG share a PCI BAR, triggering a kernel warning. The input does not describe an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with the NTB EPF driver should check their exposure; affected versions are not specified.