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-46186Bluetooth: virtio_bt: validate rx pkt_type header length

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: virtio_bt: validate rx pkt_type header length virtbt_rx_handle() reads the leading pkt_type byte from the RX skb and forwards the remainder to hci_recv_frame() for every event/ACL/SCO/ISO type, without checking that the remaining payload is at least the fixed HCI header for that type. After the preceding patch bounds the backend-supplied used.len to [1, VIRTBT_RX_BUF_SIZE], a one-byte completion still reaches hci_recv_frame() with skb->len already pulled to 0. If the byte happened to be HCI_ACLDATA_PKT, the ACL-vs-ISO classification fast-path in hci_dev_classify_pkt_type() dereferences hci_acl_hdr(skb)->handle whenever the HCI device has an active CIS_LINK, BIS_LINK, or PA_LINK connection, reading two bytes of uninitialized RX-buffer data. The same hazard exists for every packet type the driver accepts because none of the switch cases in virtbt_rx_handle() check skb->len against the per-type minimum HCI header size before handing the frame to the core. After stripping pkt_type, require skb->len to cover the fixed header size for the selected type (event 2, ACL 4, SCO 3, ISO 4) before calling hci_recv_frame(); drop ratelimited otherwise. Unknown pkt_type values still take the original kfree_skb() default path. Use bt_dev_err_ratelimited() because both the length and pkt_type values come from an untrusted backend that can otherwise flood the kernel log.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 17 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

CVSS scores of CVE-2026-46186, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected cf2719a21fdb9d4c8e9c834d279163609bef575d – < 149cfb42ad69c7964fd9f2c43831da9152007129
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < 7b2d4c04816cdc887f472caaf7fc966cfc107e40
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < 1e1e509b6fd2a42421745bbcd98bd16daad20904
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < 2c1143564c71e7497b42d8360a8379ccbb011d3c
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < 3485c7236c59c8c34a41af1c4b52982437554e79
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < f743eab6486965f276c7e3f1700895f014fdc6db
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < daf23014e5d975e72ea9c02b5160d3fcf070ea47
    • affected 9b67438e315b925a699f0178f4a48baf3d2d6ef4
    • affected 5.15.78 – < 5.15.209
    • affected 6.0.8 – < 6.1
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.88 – ≤ 6.12.*
    • unaffected 6.18.30 – ≤ 6.18.*
    • unaffected 7.0.7 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .