CVE-2026-98805: Linux kernel · tipc: prevent GCM nonce reuse on peer key changes
Source GCVE Database
Not known to be exploited · fixed in f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0, a85a3dce4b6c73ddaa1e9725b906249744bf7cf2, 512ccd3d0e91e791fb37442aa0a2599aca19783d +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to prevent nonce reuse by using a shared atomic counter for nonce generation that persists across peer key changes. Users should apply the updated Linux kernel version containing this fix. Since this is a kernel-level vulnerability, upgrading to the patched kernel version is the recommended remediation. No additional mitigations are indicated.
Description
A vulnerability in the Linux kernel's TIPC protocol allowed reuse of AES-GCM nonces when peer keys changed, breaking confidentiality and enabling trivial forgeries. The issue was fixed by changing nonce generation to use a shared atomic counter that persists across key changes, preventing nonce reuse. This fix maintains compatibility with existing receivers and prevents key revocation except in rare counter wrap scenarios.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98805 (opens in a new tab)
- git.kernel.org/stable/c/512ccd3d0e91e791fb37442aa0a2599aca19783d (opens in a new tab)
- git.kernel.org/stable/c/5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2 (opens in a new tab)
- git.kernel.org/stable/c/60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c (opens in a new tab)
- git.kernel.org/stable/c/f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0 (opens in a new tab)
- git.kernel.org/stable/c/a85a3dce4b6c73ddaa1e9725b906249744bf7cf2 (opens in a new tab)