iommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6166cb1344f16dd403f2192f4bea6f6654f1ae1e, Kernel 8646f00ce021e49f4f05bc1d4060a0c27b25d0e1, Kernel db50fb87015b955a5a0c155293b2dd40d63a3b9e and 2 more.
In the Linux kernel, the following vulnerability has been resolved: iommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path In iommu_dma_map_sg(), when handling PCI P2PDMA cases, the DMA length of the current scatterlist segment `s` is incorrectly assigned from the head entry `sg->length` instead of the current entry `s->length`. This typo causes all P2PDMA segments in the scatterlist to inherit the length of the first segment, leading to corrupted DMA lengths for multi- segment scatterlists. Fix this by using `s->length` instead of `sg->length`.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=a25e7962db0d79882c9d32fd2a67a02e79129c0e <6166cb1344f16dd403f2192f4bea6f6654f1ae1e, >=a25e7962db0d79882c9d32fd2a67a02e79129c0e <8646f00ce021e49f4f05bc1d4060a0c27b25d0e1, >=a25e7962db0d79882c9d32fd2a67a02e79129c0e <db50fb87015b955a5a0c155293b2dd40d63a3b9e | 6166cb1344f16dd403f2192f4bea6f6654f1ae1e, 8646f00ce021e49f4f05bc1d4060a0c27b25d0e1, db50fb87015b955a5a0c155293b2dd40d63a3b9e |
| linux-kernel: Kernel | >=6.16.0 <6.18.57, >=6.19.0 <7.1.5 | 6.18.57, 7.1.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket