net: devmem: reject dma-buf bind with non-page-aligned size or SG length
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 |
|
|
6.18.357.0.117.1In the Linux kernel, the following vulnerability has been resolved:
net: devmem: reject dma-buf bind with non-page-aligned size or SG length
net_devmem_bind_dmabuf() trusts dmabuf->size and sg_dma_len() to be PAGE_SIZE multiples without checking:
- tx_vec is sized dmabuf->size / PAGE_SIZE, and net_devmem_get_niov_at() only bounds-checks virt_addr < dmabuf->size before indexing tx_vec[virt_addr / PAGE_SIZE]. With size = N*PAGE_SIZE + r (1 <= r < PAGE_SIZE), sendmsg() at iov_base = N*PAGE_SIZE passes the bound check and reads tx_vec[N] -- one past.
- owner->area.num_niovs = len / PAGE_SIZE while gen_pool_add_owner() covers the full byte len, so a non-page-multiple non-final sg desyncs num_niovs from the gen_pool region for every later sg, on both RX and TX.
dma-buf does not require page-aligned sizes, so the bind path has to enforce what its own indexing assumes. Reject both with -EINVAL.
The size check is TX-only (only tx_vec is sized off dmabuf->size); the SG-length check covers both directions.
From the CVE record · Linux
Linux kernel net devmem dma-buf binding does not check that the dma-buf size or scatter-gather lengths are page-aligned. A non-page-aligned dma-buf size can lead to an out-of-bounds read during sendmsg() on the TX path; a non-page-aligned scatter-gather length can desynchronize region tracking on both RX and TX. Exploitation requires binding a dma-buf with one of these sizes; the input does not specify authentication or network-access requirements.
Engineers running Linux kernels that use net devmem dma-buf binding should check whether their kernel includes the fix; affected versions are not specified.