Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90090Bluetooth: btmtksdio: Fix out-of-bounds DMA read in the TX path

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtksdio: Fix out-of-bounds DMA read in the TX path btmtksdio_tx_packet() rounds the transfer size up to the SDIO block size of 256 bytes, but hands the host controller the SKB buffer as is: err = sdio_writesb(bdev->func, MTK_REG_CTDR, skb->data, round_up(skb->len, MTK_SDIO_BLOCK_SIZE)); Only skb->len bytes hold packet data, so the controller reads up to 255 bytes of uninitialised memory and sends it to the device over the SDIO bus. Depending on how much tailroom slack the SKB allocation happens to carry, that read can also extend past the end of the buffer. Compute the padded length up front, ensure the SKB has tailroom for it, and zero-fill the padding with skb_put_zero(). skb->len then covers the padding, so sdio_writesb() no longer needs to round up. byte_tx keeps counting the header and the payload only, and the error path restores the SKB so that the caller can requeue it. Writing behind skb->tail is only safe because the driver owns the buffer, which "Bluetooth: btmtksdio: Take exclusive ownership of the SKB before TX" ensures.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < c8742f53c9ef623decd5285403df0e5b5273c9fd
    • affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < 0b71a6caaf284915c8cf9cd320ecee9f0361824a
    • affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < 9a785ea864214aaffd8300683825c3f788d0b634
    • affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < 7b37556d7d801b79096c7ba8ea92db2338aa8b00
    • affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < 7b80d2701a68456c536f82e577dbed2f60ccb82b
    • affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < fa0ad2d277c7adead61d1c22411c55cea6990c2a
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90090 badge
[![CVE-2026-90090](https://cveledger.app/badge/CVE-2026-90090.svg)](https://cveledger.app/cve/CVE-2026-90090)

Record last updated .