{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90323 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90323 is a denial of service vulnerability in Linux, published on 17 Sep 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-90323 and fix it if it is affected.\n\nWhat it is: CVE-2026-90323 is a denial of service vulnerability in Linux, published on 17 Sep 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-90323 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-90323/ (Markdown: https://insights.sbomify.com/CVE-2026-90323/index.md)","id":"CVE-2026-90323","markdown":"https://insights.sbomify.com/CVE-2026-90323/index.md","name":"CVE-2026-90323","record":{"aliases":["BELL-CVE-2026-90323","DEBIAN-CVE-2026-90323","GHSA-rq26-mw8f-3hjh","UBUNTU-CVE-2026-90323"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can cause a kernel hang during teardown by triggering a validation error in ublk auto buffer registration.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nublk: validate auto buf reg before taking uring_cmd\n\nWith UBLK_F_AUTO_BUF_REG, invalid sqe-\u003eaddr can fail after\nublk_fill_io_cmd() has set UBLK_IO_FLAG_ACTIVE. The uring_cmd is\ncompleted while the tag stays active, which can hang teardown.\n\nSplit validation from buffer apply so the check has no side effects,\nthen take the uring_cmd and store the already-validated buffer. Apply\nthe same order in FETCH so io-\u003ebuf is not written before __ublk_fetch()\nstate checks.","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":"ublk: validate auto buf reg before taking uring_cmd","id":"CVE-2026-90323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ublk: check import_ubuf() return value","id":"CVE-2026-90324"},"packages":[],"prev":{"headline":"ocfs2/cluster: keep heartbeat local node stable","id":"CVE-2026-90322"},"products":["Linux"],"published":"2026-09-17","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-19","vendors":["Linux"]},"summary":"A local attacker can cause a kernel hang during teardown by triggering a validation error in ublk auto buffer registration.","url":"https://insights.sbomify.com/CVE-2026-90323/"}