net: mctp: take ownership of skb in mctp_local_output
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:
net: mctp: take ownership of skb in mctp_local_output
Currently, mctp_local_output only takes ownership of skb on success, and we may leak an skb if mctp_local_output fails in specific states; the skb ownership isn't transferred until the actual output routing occurs.
Instead, make mctp_local_output free the skb on all error paths up to the route action, so it always consumes the passed skb.
From the CVE record · Linux
The Linux kernel’s MCTP local output path can leak a socket buffer when output fails in specific states. The input does not establish how an attacker could trigger the failure or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with MCTP support should check whether their kernel is affected; affected versions are not specified.