tipc: prevent GCM nonce reuse on peer key changes
Summary
| CVE | CVE-2026-98805 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:17:34 UTC |
| Updated | 2026-10-30 13:21:28 UTC |
| 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. |
Risk And Classification
EPSS: 0.001780000 probability, percentile 0.073750000 (date 2026-11-01)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 04d67f77fe3f9ec9c60db70773fb1696d0d58da8 git | Not specified |
| CNA | Linux | Linux | affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 7e5d5ac25e0857548cac963a2f850b19b2e1d59c git | Not specified |
| CNA | Linux | Linux | affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 0ff0ca5b514ceecad68b8682e072f373acc5acec git | Not specified |
| CNA | Linux | Linux | affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 a85a3dce4b6c73ddaa1e9725b906249744bf7cf2 git | Not specified |
| CNA | Linux | Linux | affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2 git | Not specified |
| CNA | Linux | Linux | affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0 git | Not specified |
| CNA | Linux | Linux | affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c git | Not specified |
| CNA | Linux | Linux | affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 512ccd3d0e91e791fb37442aa0a2599aca19783d git | Not specified |
| CNA | Linux | Linux | affected 5.5 | Not specified |
| CNA | Linux | Linux | unaffected 5.5 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.273 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.224 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.191 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.113 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.56 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.10 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/7e5d5ac25e0857548cac963a2f850b19b2e1d59c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/512ccd3d0e91e791fb37442aa0a2599aca19783d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0ff0ca5b514ceecad68b8682e072f373acc5acec | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/04d67f77fe3f9ec9c60db70773fb1696d0d58da8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a85a3dce4b6c73ddaa1e9725b906249744bf7cf2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.