s390/qeth: validate user buffer length in SNMP and ARP query ioctls
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4a71df50047f0db65ea09b1be155852e81a45eba · < a3083647747942ea32faf14560d6397ff3068046| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/qeth: validate user buffer length in SNMP and ARP query ioctls
qeth_snmp_command() and qeth_l3_arp_query() allocate a buffer sized by a user-supplied length (udata_len) without checking a lower bound, then set udata_offset to a fixed non-zero value and pass both to a reply callback. The callback bounds-checks the copy with
if ((udata_len - udata_offset) < len)
Both fields are u32, so a udata_len smaller than udata_offset makes the subtraction wrap and the check pass, and the following memcpy() writes past the allocation. A udata_len of 0 also yields ZERO_SIZE_PTR from kzalloc(), which the existing NULL check does not catch.
Reject buffers smaller than udata_offset before allocating, so the callback subtraction can no longer underflow.
From the CVE record · Linux
The Linux kernel’s s390/qeth SNMP and ARP query ioctls do not validate a user-supplied buffer length before allocating memory. A local caller able to issue these ioctls can supply a length smaller than the fixed offset, causing an out-of-bounds write in a reply callback. Authentication requirements are not specified.
Engineers running Linux kernels with the s390/qeth driver should check their kernels; affected versions are not specified.