{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90251 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90251 is a 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-90251 and fix it if it is affected.\n\nWhat it is: CVE-2026-90251 is a 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-90251 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-90251/ (Markdown: https://insights.sbomify.com/CVE-2026-90251/index.md)","id":"CVE-2026-90251","markdown":"https://insights.sbomify.com/CVE-2026-90251/index.md","name":"CVE-2026-90251","record":{"aliases":["AZL-102443","BELL-CVE-2026-90251","DEBIAN-CVE-2026-90251","GHSA-hmjm-jgv8-x76g","UBUNTU-CVE-2026-90251"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Bluetooth","requires_auth":"none","summary":"A malicious Bluetooth controller can cause the Linux kernel to read uninitialized memory, potentially disclosing sensitive kernel data to the attacker.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\nBluetooth: MSFT: validate evt_prefix_len against the response length\n\nread_supported_features() only checks that the response covers the fixed\npart of struct msft_rp_read_supported_features, which is 11 bytes:\n\n\tif (skb-\u003elen \u003c sizeof(*rp)) {\n\t\tbt_dev_err(hdev, \"MSFT supported features length mismatch\");\n\t\tgoto failed;\n\t}\n\nevt_prefix[] is a flexible array member and rp-\u003eevt_prefix_len is an\nunvalidated u8 taken straight out of that response, so\n\n\tmsft-\u003eevt_prefix = kmemdup(rp-\u003eevt_prefix, rp-\u003eevt_prefix_len,\n\t\t\t\t   GFP_KERNEL);\n\ncopies up to 255 bytes from a reply that may have carried none of them.\nWhat is copied is data the controller never sent, and it is then used to\nmatch incoming vendor events in msft_vendor_evt().\n\nThis is not an out-of-bounds access. An skb data allocation always has\nat least SKB_DATA_ALIGN(sizeof(struct skb_shared_info)) bytes past the\npayload, which is more than the 255 byte maximum, so the read stays\ninside the allocation and KASAN does not report it. It is still a read\nof bytes the host was never given, with the length fully controlled by\nthe controller.\n\nReject a response that is too short for the prefix it declares.\n\nVerified with an emulated controller over /dev/vhci on a KASAN kernel,\nwith vhci made to advertise an MSFT opcode the way btintel, btqca, btmtk\nand btrtl do unconditionally. A reply of exactly 11 bytes declaring\nevt_prefix_len = 255 reaches kmemdup and copies 255 bytes\n(\"skb-\u003elen=11 evt_prefix_len=255\", with the copied buffer dumped); since\nthe reply ends at the fixed part, all 255 come from past the end of the\nresponse. No KASAN report is produced, as expected from the allocation\nslack described above. With this patch the response is rejected with\n\"MSFT event prefix length mismatch\" and msft-\u003eevt_prefix is left unset.","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":"Bluetooth: MSFT: validate evt_prefix_len against the response length","id":"CVE-2026-90251","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Bluetooth: MGMT: free the HCI command when it is cancelled","id":"CVE-2026-90252"},"packages":[],"prev":{"headline":"bpf, cgroup: Fix storage null-ptr-deref after replacing prog","id":"CVE-2026-90250"},"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 malicious Bluetooth controller can cause the Linux kernel to read uninitialized memory, potentially disclosing sensitive kernel data to the attacker.","url":"https://insights.sbomify.com/CVE-2026-90251/"}