net: mctp: ensure our nlmsg responses are initialised
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 583be982d93479ea3d85091b0fd0b01201ede87d · < 6fb6a97c86abb8592158088afaea0eb464cf9de1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: mctp: ensure our nlmsg responses are initialised
Syed Faraz Abrar (@farazsth98) from Zellic, and Pumpkin (@u1f383) from DEVCORE Research Team working with Trend Micro Zero Day Initiative report that a RTM_GETNEIGH will return uninitalised data in the pad bytes of the ndmsg data.
Ensure we're initialising the netlink data to zero, in the link, addr and neigh response messages.
From the CVE record · Linux
Linux kernel MCTP netlink responses can contain uninitialized data in the padding bytes of an ndmsg returned by RTM_GETNEIGH. Someone able to make that request may receive those bytes; the input does not specify authentication requirements or whether access is local or remote.
Operators running Linux kernels with MCTP support should check their versions; affected versions are not specified.