{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89632 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89632 is a high-severity 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-89632 and fix it if it is affected.\n\nWhat it is: CVE-2026-89632 is a high-severity 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-89632 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-89632/ (Markdown: https://insights.sbomify.com/CVE-2026-89632/index.md)","id":"CVE-2026-89632","markdown":"https://insights.sbomify.com/CVE-2026-89632/index.md","name":"CVE-2026-89632","record":{"aliases":["AZL-100757","BELL-CVE-2026-89632","DEBIAN-CVE-2026-89632","GHSA-j6wx-7c3w-595c","UBUNTU-CVE-2026-89632"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel SMB client","requires_auth":"none","summary":"A malicious SMB server can cause a kernel crash by sending a small response, leading to a use-before-check vulnerability in the Linux kernel SMB client.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix use-before-check of ReparseDataLength in reparse_buf_ptr()\n\nreparse_buf_ptr() reads buf-\u003eReparseDataLength before checking that\ncount covers the full fixed header:\n\n    buf = (struct reparse_data_buffer *)((u8 *)io + off);\n    len = sizeof(*buf);                          /* 8 bytes */\n    rdlen = le16_to_cpu(buf-\u003eReparseDataLength); /* offset 4, 2 bytes */\n\n    if (count \u003c len || count \u003c rdlen + len)      /* check comes after */\n\nstruct reparse_data_buffer has ReparseDataLength at offset 4.  If a\nserver returns OutputCount \u003c 6, the read at offset 4-5 reaches past\nthe end of the received data.  The off+count bounds against iov_len\nwere already validated, but that does not protect against count being\nsmaller than sizeof(*buf).\n\nSplit the check: verify count \u003e= sizeof(*buf) before reading\nReparseDataLength, then verify count covers the data region.","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: fix use-before-check of ReparseDataLength in reparse_buf_ptr()","id":"CVE-2026-89632","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()","id":"CVE-2026-89633"},"packages":[],"prev":{"headline":"smb: client: reject a tree connect response whose byte count is too small","id":"CVE-2026-89631"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A malicious SMB server can cause a kernel crash by sending a small response, leading to a use-before-check vulnerability in the Linux kernel SMB client.","url":"https://insights.sbomify.com/CVE-2026-89632/"}