CVE-2026-98805

tipc: prevent GCM nonce reuse on peer key changes

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.

Key facts

Published
18 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.179% likely to be exploited in the next 30 days, higher than 7.517% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 up to but excluding 04d67f77fe3f9ec9c60db70773fb1696d0d58da8 (affected)
  • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 up to but excluding 7e5d5ac25e0857548cac963a2f850b19b2e1d59c (affected)
  • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 up to but excluding 0ff0ca5b514ceecad68b8682e072f373acc5acec (affected)
  • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 up to but excluding a85a3dce4b6c73ddaa1e9725b906249744bf7cf2 (affected)
  • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 up to but excluding 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2 (affected)
  • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 up to but excluding f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0 (affected)
  • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 up to but excluding 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c (affected)
  • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 up to but excluding 512ccd3d0e91e791fb37442aa0a2599aca19783d (affected)
LinuxLinux
  • Default status: affected
  • 5.5 (affected)
  • 0 up to but excluding 5.5 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.56 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References