CVE-2026-98097
tipc: Dont send random pad bytes in RESET/ACTIVATE messages
Using Linux by Linux?
Get instant alerts when new vulnerabilities affect Linux - before attackers find them.
Description
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
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
- https://git.kernel.org/stable/c/48033a89356b8ae21a94db70c79bb6fcc91a23c2
- https://git.kernel.org/stable/c/4ab2977323d5f068a872126f7818d1aeb9e9ca0d
- https://git.kernel.org/stable/c/bee1459e57f2e0bd240c62f35c0a284291e27971
- https://git.kernel.org/stable/c/81c600c26302a27852ed8b19c5f2f647ea3555c9
- https://git.kernel.org/stable/c/3dbb628cfc592a4148d8136dcda1f706cdcad4f3
References (5)
CVSS
- Attack Vector
- NETWORK
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- LOW
- Integrity
- NONE
- Availability
- NONE
Quick Info
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.