{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89969 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89969 is a critical memory corruption vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89969 and fix it if it is affected.\n\nWhat it is: CVE-2026-89969 is a critical memory corruption vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89969 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-89969/ (Markdown: https://insights.sbomify.com/CVE-2026-89969/index.md)","id":"CVE-2026-89969","markdown":"https://insights.sbomify.com/CVE-2026-89969/index.md","name":"CVE-2026-89969","record":{"aliases":["AZL-101600","BELL-CVE-2026-89969","DEBIAN-CVE-2026-89969","GHSA-pcvm-4g32-rvg7","UBUNTU-CVE-2026-89969"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A remote unauthenticated attacker can trigger an out-of-bounds write in the Linux kernel's nvmet-tcp module by sending a crafted PDU, potentially leading to memory corruption and code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fix out-of-bounds write when receiving an over-long PDU\n\nnvmet_tcp_try_recv_pdu() reads a PDU header into the fixed 128-byte\nqueue-\u003epdu union, then computes the remaining payload length as\n\n\tqueue-\u003eleft = hdr-\u003ehlen - queue-\u003eoffset + hdgst;\n\nand reads that many more bytes into \u0026queue-\u003epdu + queue-\u003eoffset, without\never bounding the result against sizeof(queue-\u003epdu).\n\nA struct nvme_tcp_icreq_pdu is itself 128 bytes, exactly the size of the\nunion. Once a header digest has been negotiated (hdgst = 4), a second\nICReq passes the hlen == nvmet_tcp_pdu_size() check but yields\nqueue-\u003eleft = 128 - 8 + 4 = 124, so bytes 8..132 are written into the\n128-byte buffer -- 4 bytes past its end, over queue-\u003ehdr_digest and\nqueue-\u003edata_digest. Those bytes are attacker-controlled (an ICReq\ncarries no digest), and the duplicate ICReq is only rejected later,\nafter the overflow. A remote unauthenticated host can thus corrupt\nkernel memory adjacent to the receive buffer.\n\nReject any PDU whose declared length would read past the end of\nqueue-\u003epdu before the second recv.","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":"nvmet-tcp: fix out-of-bounds write when receiving an over-long PDU","id":"CVE-2026-89969","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"nvmet-auth: Synchronize timeout work during SQ teardown","id":"CVE-2026-89970"},"packages":[],"prev":{"headline":"nvmet-tcp: reject unsolicited H2CData PDUs","id":"CVE-2026-89968"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A remote unauthenticated attacker can trigger an out-of-bounds write in the Linux kernel's nvmet-tcp module by sending a crafted PDU, potentially leading to memory corruption and code execution.","url":"https://insights.sbomify.com/CVE-2026-89969/"}