{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90257 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90257 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-90257 and fix it if it is affected.\n\nWhat it is: CVE-2026-90257 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-90257 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-90257/ (Markdown: https://insights.sbomify.com/CVE-2026-90257/index.md)","id":"CVE-2026-90257","markdown":"https://insights.sbomify.com/CVE-2026-90257/index.md","name":"CVE-2026-90257","record":{"aliases":["AZL-102251","BELL-CVE-2026-90257","DEBIAN-CVE-2026-90257","GHSA-jc9v-mfxc-m9mm","UBUNTU-CVE-2026-90257"],"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 local attacker with Bluetooth access can trigger an out-of-bounds read in the Linux kernel, leaking adjacent memory contents to logs.","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: virtio_bt: avoid OOB read of build info string\n\nThe virtbt_setup_zephyr() sends the Zephyr vendor command 0xfc08 (Read\nBuild Information) and hands the response to bt_dev_info() and\nhci_set_fw_info() as a \"%s\" string starting at skb-\u003edata + 1, without\nchecking the length. A backend that answers with status only leaves that\npointer past the end of the received data, so the walk reads adjacent\nslab memory until it meets a NUL. Those bytes reach the kernel log and\nthe firmware-info debugfs file.\n\nTo fix this, print the string with a bounded \"%.*s\" limited to\nskb-\u003elen - 1. A short or unterminated response then prints as much as\narrived instead of failing setup.\n\nThis mirrors commit dd068ef04412 (\"Bluetooth: bpa10x: avoid OOB read of\nrevision string in bpa10x_setup()\"), which fixed the identical pattern.","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: virtio_bt: avoid OOB read of build info string","id":"CVE-2026-90257","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"pinctrl: airoha: add missed IRQ resource helpers","id":"CVE-2026-90258"},"packages":[],"prev":{"headline":"Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind","id":"CVE-2026-90256"},"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 with Bluetooth access can trigger an out-of-bounds read in the Linux kernel, leaking adjacent memory contents to logs.","url":"https://insights.sbomify.com/CVE-2026-90257/"}