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().
Published: 2026-09-25
Score: n/a
EPSS: n/a
KEV: No
Impact: Information Disclosure
Action: Patch Immediately
AI Analysis

Impact

This vulnerability arises in the Linux kernel TIPC networking subsystem. The unnecessary strcpy call copies the interface name into a fixed‑size buffer without ensuring the remaining padding bytes are set to zero. The previously left‑over data from the original socket buffer was transmitted to remote peers in RESET/ACTIVATE messages, allowing sensitive kernel data to leak over the network. The weakness is a classic case of information exposure from uninitialized memory.

Affected Systems

All Linux kernel installations that have not yet applied the fix, regardless of distribution, are potentially affected. No specific kernel version range was supplied in the advisory, so assume any kernel generation before the patch may be vulnerable.

Risk and Exploitability

The vulnerability is classified as information disclosure. No CVSS score or EPSS value is available, and it is not listed in the CISA KEV catalogue. The attack vector is inferred to be local; the bug only manifests when the kernel sends RESET/ACTIVATE messages, which generally requires kernel‑level privilege or an attacker that can inject code into the kernel. Consequently the likelihood of exploitation is low for a remote attacker but higher if local privilege escalation can be achieved.

Generated by OpenCVE AI on September 25, 2026 at 16:04 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the patch correcting the padding in TIPC messages.
  • If an immediate kernel upgrade is not possible, validate that the system does not use the TIPC protocol; consider disabling or removing the TIPC module to eliminate the vulnerable code path.
  • Continuously monitor vendor advisories for any updates or additional mitigations related to TIPC and apply them promptly.

Generated by OpenCVE AI on September 25, 2026 at 16:04 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 25 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200

Fri, 25 Sep 2026 10:30:00 +0000

Type Values Removed Values Added
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().
Title tipc: Dont send random pad bytes in RESET/ACTIVATE messages
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-25T10:24:27.700Z

Reserved: 2026-09-25T10:19:56.076Z

Link: CVE-2026-98097

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-25T11:17:39.490

Modified: 2026-09-25T11:17:39.490

Link: CVE-2026-98097

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-25T16:15:16Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor