{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90090 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90090 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-90090 and fix it if it is affected.\n\nWhat it is: CVE-2026-90090 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-90090 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-90090/ (Markdown: https://insights.sbomify.com/CVE-2026-90090/index.md)","id":"CVE-2026-90090","markdown":"https://insights.sbomify.com/CVE-2026-90090/index.md","name":"CVE-2026-90090","record":{"aliases":["AZL-102075","BELL-CVE-2026-90090","DEBIAN-CVE-2026-90090","GHSA-v2q7-g7pp-vm78","UBUNTU-CVE-2026-90090"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Bluetooth driver","requires_auth":"none","summary":"A local attacker with Bluetooth access can read uninitialized kernel memory via an out-of-bounds DMA read in the MediaTek SDIO Bluetooth driver.","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: btmtksdio: Fix out-of-bounds DMA read in the TX path\n\nbtmtksdio_tx_packet() rounds the transfer size up to the SDIO block size\nof 256 bytes, but hands the host controller the SKB buffer as is:\n\n\terr = sdio_writesb(bdev-\u003efunc, MTK_REG_CTDR, skb-\u003edata,\n\t\t\t   round_up(skb-\u003elen, MTK_SDIO_BLOCK_SIZE));\n\nOnly skb-\u003elen bytes hold packet data, so the controller reads up to 255\nbytes of uninitialised memory and sends it to the device over the SDIO\nbus. Depending on how much tailroom slack the SKB allocation happens to\ncarry, that read can also extend past the end of the buffer.\n\nCompute the padded length up front, ensure the SKB has tailroom for it,\nand zero-fill the padding with skb_put_zero(). skb-\u003elen then covers the\npadding, so sdio_writesb() no longer needs to round up. byte_tx keeps\ncounting the header and the payload only, and the error path restores the\nSKB so that the caller can requeue it.\n\nWriting behind skb-\u003etail is only safe because the driver owns the buffer,\nwhich \"Bluetooth: btmtksdio: Take exclusive ownership of the SKB before\nTX\" ensures.","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: btmtksdio: Fix out-of-bounds DMA read in the TX path","id":"CVE-2026-90090","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan","id":"CVE-2026-90091"},"packages":[],"prev":{"headline":"Bluetooth: btnxpuart: Validate the FW dump header length","id":"CVE-2026-90089"},"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 read uninitialized kernel memory via an out-of-bounds DMA read in the MediaTek SDIO Bluetooth driver.","url":"https://insights.sbomify.com/CVE-2026-90090/"}