{"api_version":"1","generated_at":"2026-10-21T11:24:31+00:00","cve":"CVE-2026-98805","urls":{"html":"https://cve.report/CVE-2026-98805","api":"https://cve.report/api/cve/CVE-2026-98805.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98805","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98805"},"summary":{"title":"tipc: prevent GCM nonce reuse on peer key changes","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntipc: prevent GCM nonce reuse on peer key changes\n\nTIPC can encrypt traffic between nodes using a different transmit key\nfor each node. In this mode, the AES-GCM nonce for a packet sent to a\nknown peer consists of a 32-bit prefix (a per-key salt XOR the peer's\naddress) followed by a 64-bit counter. That counter is stored in the\npeer's RX crypto object. When the peer reports a change in which key\nit uses to receive packets, TIPC resets this counter. The sender can\nstill be using the same TX key and salt, so subsequent packets reuse\nearlier nonces. This nonce reuse breaks confidentiality and exposes\nGCM's authentication key. This makes forgeries trivial: an attacker\ncan exploit CTR malleability to alter captured ciphertexts and use the\nrecovered authentication key to compute a valid tag for the modified\nciphertext, under the same key and nonce.\n\nUse the TX key's existing aead->seqno counter instead. All encryptions\nusing that key object share the same atomic counter, so concurrent\nencryptions get distinct nonce counter values. The counter survives\nkey activation and peer reconnection, and peer key-status reports\ncannot reset it. This prevents those transitions from causing nonce\nreuse while the same TX key remains installed.\n\nThe nonce format is unchanged, and receivers do not require consecutive\ncounter values, so sharing the counter across peers remains compatible\nwith existing receivers. A pre-existing check still invokes key\nrevocation in the unlikely event that the counter wraps to zero.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-18 16:17:34","updated_at":"2026-10-19 10:19:44"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/512ccd3d0e91e791fb37442aa0a2599aca19783d","name":"https://git.kernel.org/stable/c/512ccd3d0e91e791fb37442aa0a2599aca19783d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0","name":"https://git.kernel.org/stable/c/f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c","name":"https://git.kernel.org/stable/c/60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2","name":"https://git.kernel.org/stable/c/5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98805","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98805","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 512ccd3d0e91e791fb37442aa0a2599aca19783d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.5","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.5 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.113 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.56 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.10 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/tipc/crypto.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2","status":"affected","version":"fc1b6d6de2208774efd2a20bf0daddb02d18b1e0","versionType":"git"},{"lessThan":"f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0","status":"affected","version":"fc1b6d6de2208774efd2a20bf0daddb02d18b1e0","versionType":"git"},{"lessThan":"60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c","status":"affected","version":"fc1b6d6de2208774efd2a20bf0daddb02d18b1e0","versionType":"git"},{"lessThan":"512ccd3d0e91e791fb37442aa0a2599aca19783d","status":"affected","version":"fc1b6d6de2208774efd2a20bf0daddb02d18b1e0","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/tipc/crypto.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.5"},{"lessThan":"5.5","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.113","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.56","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.10","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.113","versionStartIncluding":"5.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.56","versionStartIncluding":"5.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.10","versionStartIncluding":"5.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"5.5","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ntipc: prevent GCM nonce reuse on peer key changes\n\nTIPC can encrypt traffic between nodes using a different transmit key\nfor each node. In this mode, the AES-GCM nonce for a packet sent to a\nknown peer consists of a 32-bit prefix (a per-key salt XOR the peer's\naddress) followed by a 64-bit counter. That counter is stored in the\npeer's RX crypto object. When the peer reports a change in which key\nit uses to receive packets, TIPC resets this counter. The sender can\nstill be using the same TX key and salt, so subsequent packets reuse\nearlier nonces. This nonce reuse breaks confidentiality and exposes\nGCM's authentication key. This makes forgeries trivial: an attacker\ncan exploit CTR malleability to alter captured ciphertexts and use the\nrecovered authentication key to compute a valid tag for the modified\nciphertext, under the same key and nonce.\n\nUse the TX key's existing aead->seqno counter instead. All encryptions\nusing that key object share the same atomic counter, so concurrent\nencryptions get distinct nonce counter values. The counter survives\nkey activation and peer reconnection, and peer key-status reports\ncannot reset it. This prevents those transitions from causing nonce\nreuse while the same TX key remains installed.\n\nThe nonce format is unchanged, and receivers do not require consecutive\ncounter values, so sharing the counter across peers remains compatible\nwith existing receivers. A pre-existing check still invokes key\nrevocation in the unlikely event that the counter wraps to zero."}],"providerMetadata":{"dateUpdated":"2026-10-19T09:25:58.711Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2"},{"url":"https://git.kernel.org/stable/c/f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0"},{"url":"https://git.kernel.org/stable/c/60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c"},{"url":"https://git.kernel.org/stable/c/512ccd3d0e91e791fb37442aa0a2599aca19783d"}],"title":"tipc: prevent GCM nonce reuse on peer key changes","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98805","datePublished":"2026-10-18T15:48:51.902Z","dateReserved":"2026-09-25T10:25:14.371Z","dateUpdated":"2026-10-19T09:25:58.711Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-18 16:17:34","lastModifiedDate":"2026-10-19 10:19:44","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98805","Ordinal":"1","Title":"tipc: prevent GCM nonce reuse on peer key changes","CVE":"CVE-2026-98805","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98805","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ntipc: prevent GCM nonce reuse on peer key changes\n\nTIPC can encrypt traffic between nodes using a different transmit key\nfor each node. In this mode, the AES-GCM nonce for a packet sent to a\nknown peer consists of a 32-bit prefix (a per-key salt XOR the peer's\naddress) followed by a 64-bit counter. That counter is stored in the\npeer's RX crypto object. When the peer reports a change in which key\nit uses to receive packets, TIPC resets this counter. The sender can\nstill be using the same TX key and salt, so subsequent packets reuse\nearlier nonces. This nonce reuse breaks confidentiality and exposes\nGCM's authentication key. This makes forgeries trivial: an attacker\ncan exploit CTR malleability to alter captured ciphertexts and use the\nrecovered authentication key to compute a valid tag for the modified\nciphertext, under the same key and nonce.\n\nUse the TX key's existing aead->seqno counter instead. All encryptions\nusing that key object share the same atomic counter, so concurrent\nencryptions get distinct nonce counter values. The counter survives\nkey activation and peer reconnection, and peer key-status reports\ncannot reset it. This prevents those transitions from causing nonce\nreuse while the same TX key remains installed.\n\nThe nonce format is unchanged, and receivers do not require consecutive\ncounter values, so sharing the counter across peers remains compatible\nwith existing receivers. A pre-existing check still invokes key\nrevocation in the unlikely event that the counter wraps to zero.","Type":"Description","Title":"tipc: prevent GCM nonce reuse on peer key changes"}]}}}