tipc: Dont send random pad bytes in RESET/ACTIVATE messages
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tipc: Dont send random pad bytes in RESET/ACTIVATE messages
The interface name is passed in a fixed length (TIPC_MAX_IF_NAME) buffer. Replace the strcpy(data, l->if_name) with memcpy() so that the pad bytes are actually written (l->if_name[] is zero padded) rather than sending random bytes from the skb to the remote system.
Replace two other strcpy() with strscpy().
From the CVE record · Linux
The Linux kernel's TIPC code can send uninitialized pad bytes from a packet buffer to a remote system in RESET/ACTIVATE messages. This occurs when the interface name is copied into a fixed-length buffer; the input does not specify an authentication requirement or user interaction.
Engineers running Linux kernels with TIPC should check their deployments; affected versions are not specified.