Description
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.
Product status
b8b7570a7ec872f2a27b775c4f8710ca8a357adf (git) before f3ed399e9aa6f36e92d2d0fe88b387915e9705fe
b8b7570a7ec872f2a27b775c4f8710ca8a357adf (git) before 071be3b0b6575d45be9df9c5b612f5882bfc5e88
6.17
Any version before 6.17
6.18.10 (semver)
6.19 (original_commit_for_fix)
References
git.kernel.org/...c/f3ed399e9aa6f36e92d2d0fe88b387915e9705fe
git.kernel.org/...c/071be3b0b6575d45be9df9c5b612f5882bfc5e88