CVE-2026-90257

Bluetooth: virtio_bt: avoid OOB read of build info string

N/A
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.13afd2daa26c7abd734d78bd274fc6c59a15e61063
Vendor states this is fixed in 0e388d805233a883a31271676eae6031dfc9e898 (fixed)
Vendor states this is fixed in 502adc06ba76dee19c292ae4a07d74d202fe734d (fixed)
Vendor states this is fixed in 54e9387eb7546eaa6f600220599d55740956ffc3 (fixed)
Vendor states this is fixed in 84ea9c99874804f5ca13f35bbc186ba93902f30f (fixed)
Vendor states this is fixed in be1e3df2c49c91b0a052c6563884e8d39bd768b2 (fixed)
Vendor states this is fixed in d08c99abf06133a7829d46627e77e3315ca974d2 (fixed)
Vendor states this is fixed in fb445b3466a8d1c7a0b0d0676fb475e3ce22d94e (fixed)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card