{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89630 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89630 is a critical vulnerability in Linux, published on 11 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-89630 and fix it if it is affected.\n\nWhat it is: CVE-2026-89630 is a critical vulnerability in Linux, published on 11 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-89630 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-89630/ (Markdown: https://insights.sbomify.com/CVE-2026-89630/index.md)","id":"CVE-2026-89630","markdown":"https://insights.sbomify.com/CVE-2026-89630/index.md","name":"CVE-2026-89630","record":{"aliases":["BELL-CVE-2026-89630","DEBIAN-CVE-2026-89630","GHSA-gch3-h386-3492","UBUNTU-CVE-2026-89630"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel SMB client","requires_auth":"none","summary":"An integer overflow in the Linux kernel SMB client allows bypassing bounds checks, potentially leading to memory corruption or denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: restore the data_offset bound in is_valid_oplock_break()\n\nCommit 83bfbd0bb902 (\"cifs: Remove the RFC1002 header from smb_hdr\")\nchanged the quantity this bound is measured against.  It used to be\nsrv-\u003etotal_read minus the 4-byte RFC1002 preamble that total_read then\nincluded, so it was the SMB message length.  The same commit stopped\ncounting the preamble, and the mechanical substitution to\nsrv-\u003etotal_read - srv-\u003epdu_size left an expression that is identically\nzero: standard_receive3() reads MID_HEADER_SIZE() bytes and then exactly\npdu_length - MID_HEADER_SIZE() more, adding both to total_read.\n\nlen is therefore 0, the subtraction below it wraps, and no __u32\nDataOffset can exceed the result, so the check from commit 097f5863b1a0\n(\"cifs: read overflow in is_valid_oplock_break()\") no longer rejects\nanything.  Use total_read, which is now the message length on its own.","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":"smb: client: restore the data_offset bound in is_valid_oplock_break()","id":"CVE-2026-89630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"smb: client: reject a tree connect response whose byte count is too small","id":"CVE-2026-89631"},"packages":[],"prev":{"headline":"HID: corsair-void: Check size of status and firmware events before reading them","id":"CVE-2026-89629"},"products":["Linux"],"published":"2026-09-11","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":"An integer overflow in the Linux kernel SMB client allows bypassing bounds checks, potentially leading to memory corruption or denial of service.","url":"https://insights.sbomify.com/CVE-2026-89630/"}