CVE-2026-98805: tipc: prevent GCM nonce reuse on peer key changes
Vulnerability summary
CVE-2026-98805 is a critical (CVSS 9.1) vulnerability in linux. EPSS estimates a 0.18% chance of exploitation in the next 30 days, higher than 7.6% of scored vulnerabilities.
Severe, CVSS 9.1 (OSV · Ubuntu); no exploitation reported by the 5 checked sources; EPSS 0% (FIRST, 20-11-2026)
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 22 · Related 19Timeline
- 18-10-2026PublishedVulnerability first disclosed.
- 30-10-2026Last modifiedVulnerability information updated.
Description
In the Linux kernel, the following vulnerability has been resolved: tipc: prevent GCM nonce reuse on peer key changes TIPC can encrypt traffic between nodes using a different transmit key for each node. In this mode, the AES-GCM nonce for a packet sent to a known peer consists of a 32-bit prefix (a per-key salt XOR the peer's address) followed by a 64-bit counter. That counter is stored in the peer's RX crypto object. When the peer reports a change in which key it uses to receive packets, TIPC resets this counter. The sender can still be using the same TX key and salt, so subsequent packets reuse earlier nonces. This nonce reuse breaks confidentiality and exposes GCM's authentication key. This makes forgeries trivial: an attacker can exploit CTR malleability to alter captured ciphertexts and use the recovered authentication key to compute a valid tag for the modified ciphertext, under the same key and nonce. Use the TX key's existing aead->seqno counter instead. All encryptions using that key object share the same atomic counter, so concurrent encryptions get distinct nonce counter values. The counter survives key activation and peer reconnection, and peer key-status reports cannot reset it. This prevents those transitions from causing nonce reuse while the same TX key remains installed. The nonce format is unchanged, and receivers do not require consecutive counter values, so sharing the counter across peers remains compatible with existing receivers. A pre-existing check still invokes key revocation in the unlikely event that the counter wraps to zero.
CVSS metrics
1 score · 1 source · 1 versionEPSS trend
Probability
0.18%
Chance of exploitation in the next 30 days
Percentile
8%
Versus all other CVEs
30-day change
Increase +0.05 pp
From 0.13% on 21-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu169 products
- linuxAll versions (No fix recorded) | < 5.15.0-204.214 | < 6.8.0-149.149 | < 7.0.0-43.43
- linux-allwinner-5.19All versions (No fix recorded)
- linux-awsAll versions (No fix recorded) | < 5.15.0-1121.128 | < 6.8.0-1069.74 | < 7.0.0-1017.18
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Debian2 products
- linuxAll versions (No fix recorded) | < 6.1.192-1 | < 6.12.113-1 | < 7.2.10-1
- linux-6.12< 6.12.113-1~deb12u1
Linux1 product
- linux≥ fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < 04d67f77fe3f9ec9c60db70773fb1696d0d58da8 | ≥ fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < 7e5d5ac25e0857548cac963a2f850b19b2e1d59c | ≥ fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < 0ff0ca5b514ceecad68b8682e072f373acc5acec | ≥ fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < a85a3dce4b6c73ddaa1e9725b906249744bf7cf2 | ≥ fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2 | ≥ fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0 | ≥ fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c | ≥ fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < 512ccd3d0e91e791fb37442aa0a2599aca19783d | 5.5
3 vendors · 172 products