dma-buf: Fix silent overflow for phys vec to sgt
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dma-buf: Fix silent overflow for phys vec to sgt
In case MMIO size is bigger than 4G and peer2peer DMA goes through host bridge, we trigger a code path that assigns the total linked IOVA (which is greater than 4G) to mapped_len.
Previously, `mapped_len` was declared as 32-bit `unsigned int`. When accumulating `size_t` lengths, this leads to a silent wrap-around. This truncation causes truncated lengths to be passed to functions like `fill_sg_entry()`.
Fix this by changing `mapped_len` to `size_t` (64-bit). While at it, fix similar potential overflow issues in `calc_sg_nents` by using `check_add_overflow()` for `nents` and using `unsigned int` for the loop iterator in `fill_sg_entry` to match.
From the CVE record · Linux
The Linux kernel’s dma-buf code can silently overflow a length value when MMIO size exceeds 4 GB and peer-to-peer DMA passes through a host bridge. This can cause truncated lengths to be passed to functions such as fill_sg_entry(). The input does not describe an attacker action, authentication requirement, or user interaction.
Operators running the Linux kernel should check whether their kernel includes this issue; affected versions are not specified.