CVE-2026-46123: Bluetooth: virtio_bt: clamp rx length before skb_put
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 21bd244b6de5d2fe1063c23acc93fbdd2b20d112, 4236e55b2d9d1ffd3b4bdf8ebbb86e5a0a526b4a, 5.15.209; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 21bd244b6de5d2fe1063c23acc93fbdd2b20d112, 4236e55b2d9d1ffd3b4bdf8ebbb86e5a0a526b4a, 5.15.209; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 28, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-787
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 9b67438e315b925a699f0178f4a48baf3d2d6ef4, 6.1affected
- cf2719a21fdb9d4c8e9c834d279163609bef575d and later · before 4236e55b2d9d1ffd3b4bdf8ebbb86e5a0a526b4aaffected · git
- 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be and later · before fd91fa2678ab603dfb285416c1cf3843d7be1e41affected · git
- 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be and later · before ed41c81d30b211a671667259c3b5feeba0e062d5affected · git
- 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be and later · before 6c1730099a6fc18b183bd6c1adad3b54adcaeda9affected · git
- 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be and later · before b40cdd1b1370d76e9e760af4490cb4a351cceeadaffected · git
- 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be and later · before e6b4296f170d949ebba937cf6a3f247ec9550d2caffected · git
- 160fbcf3bfb93c3c086427f9f4c8bc70f217e9be and later · before 21bd244b6de5d2fe1063c23acc93fbdd2b20d112affected · git
- 5.15.78 and later · before 5.15.209affected · semver
- 6.0.8 and later · before 6.1affected · semver
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15.78 and later · before 5.15.209
- linux linux kernel6.0.8 and later · before 6.1
- linux linux kernel6.1.1 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.140
- linux linux kernel6.7 and later · before 6.12.88
- linux linux kernel6.13 and later · before 6.18.30
- linux linux kernel6.19 and later · before 7.0.7
- linux linux kernel6.1
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46108May 28, 2026 · ipmi:si: Return state to normal if message allocation fails22Monitor
- ← EarlierCVE-2026-46112May 28, 2026 · RDMA/hns: Fix unlocked call to hns_roce_qp_remove()31Monitor
- Later →CVE-2026-46129May 28, 2026 · btrfs: fix double free in create_space_info() error path31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 21bd244b6de5d2fe1063c23acc93fbdd2b20d112 | Vendor (CNA) |
| Linux Linux | 4236e55b2d9d1ffd3b4bdf8ebbb86e5a0a526b4a | Vendor (CNA) |
| Linux Linux | 5.15.209 | Vendor (CNA) |
| Linux Linux | 6.1 | Vendor (CNA) |
| Linux Linux | 6c1730099a6fc18b183bd6c1adad3b54adcaeda9 | Vendor (CNA) |
| Linux Linux | b40cdd1b1370d76e9e760af4490cb4a351cceead | Vendor (CNA) |
| Linux Linux | e6b4296f170d949ebba937cf6a3f247ec9550d2c | Vendor (CNA) |
| Linux Linux | ed41c81d30b211a671667259c3b5feeba0e062d5 | Vendor (CNA) |
| Linux Linux | fd91fa2678ab603dfb285416c1cf3843d7be1e41 | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.141.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+17
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/4236e55b2d9d1ffd3b4bdf8ebbb86e5a0a526b4a
- git.kernel.org/stable/c/6c1730099a6fc18b183bd6c1adad3b54adcaeda9
- git.kernel.org/stable/c/b40cdd1b1370d76e9e760af4490cb4a351cceead
- git.kernel.org/stable/c/e6b4296f170d949ebba937cf6a3f247ec9550d2c
- git.kernel.org/stable/c/ed41c81d30b211a671667259c3b5feeba0e062d5
- git.kernel.org/stable/c/fd91fa2678ab603dfb285416c1cf3843d7be1e41
Vendor advisories and official records. Exploit/PoC links are deliberately left out.