iommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.57, 7.1.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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`.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From a25e7962db0d79882c9d32fd2a67a02e79129c0e · fixed in 6166cb1344f16dd403f2192f4bea6f6654f1ae1e; From a25e7962db0d79882c9d32fd2a67a02e79129c0e · fixed in 8646f00ce021e49f4f05bc1d4060a0c27b25d0e1; From a25e7962db0d79882c9d32fd2a67a02e79129c0e · fixed in db50fb87015b955a5a0c155293b2dd40d63a3b9e
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.1.5