tipc: Dont send random pad bytes in RESET/ACTIVATE messages
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.111, 6.18.53, 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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().
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From e74a386d70c793ef44678b44b021c99094b28c47 · fixed in 3dbb628cfc592a4148d8136dcda1f706cdcad4f3; From e74a386d70c793ef44678b44b021c99094b28c47 · fixed in 48033a89356b8ae21a94db70c79bb6fcc91a23c2; From e74a386d70c793ef44678b44b021c99094b28c47 · fixed in 4ab2977323d5f068a872126f7818d1aeb9e9ca0d; From e74a386d70c793ef44678b44b021c99094b28c47 · fixed in bee1459e57f2e0bd240c62f35c0a284291e27971; From e74a386d70c793ef44678b44b021c99094b28c47 · fixed in 81c600c26302a27852ed8b19c5f2f647ea3555c9
- Linux Linux
4.6
- KernelLinux
From 4.6.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7