{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98805 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98805 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98805 and fix it if it is affected.\n\nWhat it is: CVE-2026-98805 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98805 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98805/ (Markdown: https://insights.sbomify.com/CVE-2026-98805/index.md)","id":"CVE-2026-98805","markdown":"https://insights.sbomify.com/CVE-2026-98805/index.md","name":"CVE-2026-98805","record":{"aliases":["AZL-108590","BELL-CVE-2026-98805","DEBIAN-CVE-2026-98805","GHSA-c3cw-v3mg-q5gm","UBUNTU-CVE-2026-98805"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel TIPC","requires_auth":"none","summary":"An attacker on the network can decrypt and forge TIPC traffic due to nonce reuse when peer keys change, compromising confidentiality and integrity.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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-\u003eseqno 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"tipc: prevent GCM nonce reuse on peer key changes","id":"CVE-2026-98805","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled","id":"CVE-2026-98806"},"packages":[],"prev":{"headline":"net: page_pool: fix use-after-free in page_pool_recycle_ring_bulk()","id":"CVE-2026-98804"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"An attacker on the network can decrypt and forge TIPC traffic due to nonce reuse when peer keys change, compromising confidentiality and integrity.","url":"https://insights.sbomify.com/CVE-2026-98805/"}