VulnerabilityPublished 25 Sep 2026Updated 28 Oct 2026

CVE-2026-98097: Linux kernel · tipc: Dont send random pad bytes in RESET/ACTIVATE messages

Source GCVE Database

Authoritative record:CVE-2026-98097· Medium

Not known to be exploited · CVSS 5.3 Medium · fixed in bee1459e57f2e0bd240c62f35c0a284291e27971 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 22:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in bee1459e57f2e0bd240c62f35c0a284291e27971, 48033a89356b8ae21a94db70c79bb6fcc91a23c2, 81c600c26302a27852ed8b19c5f2f647ea3555c9 +2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-3hxh-h963-cm8c

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ e74a386d70c793ef44678b44b021c99094b28c47, < bee1459e57f2e0bd240c62f35c0a284291e27971	Fixed in bee1459e57f2e0bd240c62f35c0a284291e27971
LinuxLinux	Affected ≥ e74a386d70c793ef44678b44b021c99094b28c47, < 48033a89356b8ae21a94db70c79bb6fcc91a23c2	Fixed in 48033a89356b8ae21a94db70c79bb6fcc91a23c2
LinuxLinux	Affected ≥ e74a386d70c793ef44678b44b021c99094b28c47, < 81c600c26302a27852ed8b19c5f2f647ea3555c9	Fixed in 81c600c26302a27852ed8b19c5f2f647ea3555c9
LinuxLinux	Affected ≥ e74a386d70c793ef44678b44b021c99094b28c47, < 4ab2977323d5f068a872126f7818d1aeb9e9ca0d	Fixed in 4ab2977323d5f068a872126f7818d1aeb9e9ca0d
LinuxLinux	Affected ≥ e74a386d70c793ef44678b44b021c99094b28c47, < 3dbb628cfc592a4148d8136dcda1f706cdcad4f3	Fixed in 3dbb628cfc592a4148d8136dcda1f706cdcad4f3
LinuxLinux	Affected =4.6	Fixed in–

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().

References

Community reviews

Loading reviews…