dibs: loopback: validate offset and size in move_data()
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:
dibs: loopback: validate offset and size in move_data()
The loopback move_data() performs a memcpy into the registered DMB without checking whether offset + size exceeds the DMB length. Unlike real ISM hardware, which enforces memory region bounds natively, the software loopback has no such protection.
A peer-supplied out-of-bounds offset or oversized write would result in an OOB write past the allocated kernel buffer. Add an explicit bounds check before the memcpy to reject such requests with -EINVAL.
From the CVE record · Linux
The Linux kernel's dibs loopback move_data() does not check whether a write fits within the registered DMB. A peer that supplies an out-of-bounds offset or oversized write can cause a write past the allocated kernel buffer. The input does not specify authentication or user-interaction requirements.
Engineers running the Linux kernel with dibs loopback should check their installations; affected versions are not specified.