Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98805tipc: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 – < 04d67f77fe3f9ec9c60db70773fb1696d0d58da8
    • affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 – < 7e5d5ac25e0857548cac963a2f850b19b2e1d59c
    • affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 – < 0ff0ca5b514ceecad68b8682e072f373acc5acec
    • affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 – < a85a3dce4b6c73ddaa1e9725b906249744bf7cf2
    • affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 – < 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2
    • affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 – < f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0
    • affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 – < 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c
    • affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 – < 512ccd3d0e91e791fb37442aa0a2599aca19783d
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98805 badge
[![CVE-2026-98805](https://cveledger.app/badge/CVE-2026-98805.svg)](https://cveledger.app/cve/CVE-2026-98805)

Record last updated .