nvme-pci: handle changing device dma map requirements
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 071be3b0b6575d45be9df9c5b612f5882bfc5e88 and Kernel f3ed399e9aa6f36e92d2d0fe88b387915e9705fe.
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: handle changing device dma map requirements The initial state of dma_needs_unmap may be false, but change to true while mapping the data iterator. Enabling swiotlb is one such case that can change the result. The nvme driver needs to save the mapped dma vectors to be unmapped later, so allocate as needed during iteration rather than assume it was always allocated at the beginning. This fixes a NULL dereference from accessing an uninitialized dma_vecs when the device dma unmapping requirements change mid-iteration.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=b8b7570a7ec872f2a27b775c4f8710ca8a357adf <071be3b0b6575d45be9df9c5b612f5882bfc5e88, >=b8b7570a7ec872f2a27b775c4f8710ca8a357adf <f3ed399e9aa6f36e92d2d0fe88b387915e9705fe | 071be3b0b6575d45be9df9c5b612f5882bfc5e88, f3ed399e9aa6f36e92d2d0fe88b387915e9705fe |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket