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-46123Bluetooth: virtio_bt: clamp rx length before skb_put

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: virtio_bt: clamp rx length before skb_put virtbt_rx_work() calls skb_put(skb, len) where len comes directly from virtqueue_get_buf() with no validation against the buffer we posted to the device. The RX skb is allocated in virtbt_add_inbuf() and exposed to virtio as exactly 1000 bytes via sg_init_one(). Checking len against skb_tailroom(skb) is not sufficient because alloc_skb() can leave more tailroom than the 1000 bytes actually handed to the device. A malicious or buggy backend can therefore report used.len between 1001 and skb_tailroom(skb), causing skb_put() to include uninitialized kernel heap bytes that were never written by the device. The same path also accepts len == 0, in which case skb_put(skb, 0) leaves the skb empty but virtbt_rx_handle() still reads the pkt_type byte from skb->data, consuming uninitialized memory. Define VIRTBT_RX_BUF_SIZE once and reuse it in alloc_skb() and sg_init_one(), and gate virtbt_rx_work() on that same constant so the bound checked matches the buffer actually exposed to the device. Reject used.len == 0 in the same gate so an empty completion can no longer reach virtbt_rx_handle(). Use bt_dev_err_ratelimited() because the length value comes from an untrusted backend that can otherwise flood the kernel log. Same class of bug as commit c04db81cd028 ("net/9p: Fix buffer overflow in USB transport layer"), which hardened the USB 9p transport against unchecked device-reported length.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 2 months 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-46123, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.7CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Undergoing Analysis3.1High7.7CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.14% · top 96% of all CVEs (20 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected cf2719a21fdb9d4c8e9c834d279163609bef575d – < 4236e55b2d9d1ffd3b4bdf8ebbb86e5a0a526b4a
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < fd91fa2678ab603dfb285416c1cf3843d7be1e41
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < ed41c81d30b211a671667259c3b5feeba0e062d5
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < 6c1730099a6fc18b183bd6c1adad3b54adcaeda9
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < b40cdd1b1370d76e9e760af4490cb4a351cceead
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < e6b4296f170d949ebba937cf6a3f247ec9550d2c
    • affected 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be – < 21bd244b6de5d2fe1063c23acc93fbdd2b20d112
    • 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-46123 badge
[![CVE-2026-46123](https://cveledger.app/badge/CVE-2026-46123.svg)](https://cveledger.app/cve/CVE-2026-46123)

Record last updated .