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-90257Bluetooth: virtio_bt: avoid OOB read of build info string

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: virtio_bt: avoid OOB read of build info string The virtbt_setup_zephyr() sends the Zephyr vendor command 0xfc08 (Read Build Information) and hands the response to bt_dev_info() and hci_set_fw_info() as a "%s" string starting at skb->data + 1, without checking the length. A backend that answers with status only leaves that pointer past the end of the received data, so the walk reads adjacent slab memory until it meets a NUL. Those bytes reach the kernel log and the firmware-info debugfs file. To fix this, print the string with a bounded "%.*s" limited to skb->len - 1. A short or unterminated response then prints as much as arrived instead of failing setup. This mirrors commit dd068ef04412 ("Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup()"), which fixed the identical pattern.

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 88% of all CVEs (18 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 afd2daa26c7abd734d78bd274fc6c59a15e61063 – < fb445b3466a8d1c7a0b0d0676fb475e3ce22d94e
    • affected afd2daa26c7abd734d78bd274fc6c59a15e61063 – < d08c99abf06133a7829d46627e77e3315ca974d2
    • affected afd2daa26c7abd734d78bd274fc6c59a15e61063 – < 0e388d805233a883a31271676eae6031dfc9e898
    • affected afd2daa26c7abd734d78bd274fc6c59a15e61063 – < 54e9387eb7546eaa6f600220599d55740956ffc3
    • affected afd2daa26c7abd734d78bd274fc6c59a15e61063 – < be1e3df2c49c91b0a052c6563884e8d39bd768b2
    • affected afd2daa26c7abd734d78bd274fc6c59a15e61063 – < 84ea9c99874804f5ca13f35bbc186ba93902f30f
    • affected afd2daa26c7abd734d78bd274fc6c59a15e61063 – < 502adc06ba76dee19c292ae4a07d74d202fe734d
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.221 – ≤ 5.15.*
    • 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

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .