CVE-2026-90257

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/bluetooth/virtio_bt.c

What this is

BLUETOOTH DRIVERSMAINTAINERS section matched on drivers/bluetooth/ · linux-bluetooth@vger.kernel.org · Supported

Kernel module

virtio_bt

Check it on the machine

grep -wE 'CONFIG_BT|CONFIG_BT_VIRTIO' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w virtio_bt

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian does not build this code in 3 releases. It does build it in 2 releases, so the answer depends on which release the machine runs.

• bookworm, trixien
• forky, sidMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
• bookworm · linux-6.12n

n

not enabled on any flavour - this release does not build the code

M

a module where it is built at all; some flavours do not build it

Build switches

CONFIG_BT, CONFIG_BT_VIRTIO

Reads as

all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-09-17 (31 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.21%, higher than 11.0% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/bluetooth

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
5.13	5.15.221	fb445b3466a8
5.13	6.1.188	d08c99abf061
5.13	6.6.157	0e388d805233
5.13	6.12.110	54e9387eb754
5.13	6.18.52	be1e3df2c49c
5.13	7.2.6	84ea9c998748
5.13	7.3	502adc06ba76

Debian advisories