Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-90257: Bluetooth: virtio_bt: avoid OOB read of build info string

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 0e388d805233a883a31271676eae6031dfc9e898, 502adc06ba76dee19c292ae4a07d74d202fe734d, 54e9387eb7546eaa6f600220599d55740956ffc3.

Low priority for now. Upgrade to Linux Linux 0e388d805233a883a31271676eae6031dfc9e898, 502adc06ba76dee19c292ae4a07d74d202fe734d, 54e9387eb7546eaa6f600220599d55740956ffc3 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: 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.

Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2026-90257

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi 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 help

Affected 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.

—

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

    • 5.13affected
    • afd2daa26c7abd734d78bd274fc6c59a15e61063 and later · before fb445b3466a8d1c7a0b0d0676fb475e3ce22d94eaffected · git
    • afd2daa26c7abd734d78bd274fc6c59a15e61063 and later · before d08c99abf06133a7829d46627e77e3315ca974d2affected · git
    • afd2daa26c7abd734d78bd274fc6c59a15e61063 and later · before 0e388d805233a883a31271676eae6031dfc9e898affected · git
    • afd2daa26c7abd734d78bd274fc6c59a15e61063 and later · before 54e9387eb7546eaa6f600220599d55740956ffc3affected · git
    • afd2daa26c7abd734d78bd274fc6c59a15e61063 and later · before be1e3df2c49c91b0a052c6563884e8d39bd768b2affected · git
    • afd2daa26c7abd734d78bd274fc6c59a15e61063 and later · before 84ea9c99874804f5ca13f35bbc186ba93902f30faffected · git
    • afd2daa26c7abd734d78bd274fc6c59a15e61063 and later · before 502adc06ba76dee19c292ae4a07d74d202fe734daffected · git
    • before 5.13not affected · semver
    • 5.15.221 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-90255Sep 17, 2026 · Bluetooth: hci_conn: fix the SCO setup context lifetime
    35Monitor
  • ← EarlierCVE-2026-90256Sep 17, 2026 · Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind
    35Monitor
  • Later →CVE-2026-90258Sep 17, 2026 · pinctrl: airoha: add missed IRQ resource helpers
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0e388d805233a883a31271676eae6031dfc9e898Vendor (CNA)
Linux Linux502adc06ba76dee19c292ae4a07d74d202fe734dVendor (CNA)
Linux Linux54e9387eb7546eaa6f600220599d55740956ffc3Vendor (CNA)
Linux Linux84ea9c99874804f5ca13f35bbc186ba93902f30fVendor (CNA)
Linux Linuxbe1e3df2c49c91b0a052c6563884e8d39bd768b2Vendor (CNA)
Linux Linuxd08c99abf06133a7829d46627e77e3315ca974d2Vendor (CNA)
Linux Linuxfb445b3466a8d1c7a0b0d0676fb475e3ce22d94eVendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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.

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records