tipc: Dont send random pad bytes in RESET/ACTIVATE messages
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3dbb628cfc592a4148d8136dcda1f706cdcad4f3, Kernel 48033a89356b8ae21a94db70c79bb6fcc91a23c2, Kernel 4ab2977323d5f068a872126f7818d1aeb9e9ca0d and 2 more.
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().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.6, >=e74a386d70c793ef44678b44b021c99094b28c47 <3dbb628cfc592a4148d8136dcda1f706cdcad4f3, >=e74a386d70c793ef44678b44b021c99094b28c47 <48033a89356b8ae21a94db70c79bb6fcc91a23c2, >=e74a386d70c793ef44678b44b021c99094b28c47 <4ab2977323d5f068a872126f7818d1aeb9e9ca0d, >=e74a386d70c793ef44678b44b021c99094b28c47 <81c600c26302a27852ed8b19c5f2f647ea3555c9, >=e74a386d70c793ef44678b44b021c99094b28c47 <bee1459e57f2e0bd240c62f35c0a284291e27971 | 3dbb628cfc592a4148d8136dcda1f706cdcad4f3, 48033a89356b8ae21a94db70c79bb6fcc91a23c2, 4ab2977323d5f068a872126f7818d1aeb9e9ca0d, 81c600c26302a27852ed8b19c5f2f647ea3555c9, bee1459e57f2e0bd240c62f35c0a284291e27971 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket