CVE-2026-90093: Bluetooth: L2CAP: access chan->conn safely in get/setsockopt
Noroxi assessment
Priority: Monitor (action score 31/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.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0d7b7b31ea092e17d757bd24e2e9028ba5e3a4ca, 19e154d794eb4d33d99ca4a087b1cea9d5e65786, 3af72bf8f73c519ee562e6963d5ff8e678924f93.
Low priority for now. Upgrade to Linux Linux 0d7b7b31ea092e17d757bd24e2e9028ba5e3a4ca, 19e154d794eb4d33d99ca4a087b1cea9d5e65786, 3af72bf8f73c519ee562e6963d5ff8e678924f93 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: L2CAP: access chan->conn safely in get/setsockopt Since commit b66774b48dd9 ("Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref") l2cap_chan::conn has held reference and remains non-NULL also after the corresponding hci_conn is deleted. In this state accessing various fields eg. hci_conn::hdev is invalid, which leads to KASAN crash in l2cap_sock_setsockopt() access of conn->hcon->hdev. Check l2cap_chan::conn.hcon corresponds to an alive hci_conn before trying to use it in l2cap_sock.c. Hold l2cap_chan_lock() in getsockopt/setsockopt to ensure it stays alive, and to avoid data races in l2cap_chan fields.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- 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.
Running WordPress? Scan your site free with WP Lens
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 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.
—
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
- 50c38d9f42a529691e4e67ea9cedf4f0bfc8d277, 7.2affected
- 8f90405a4a6f1f1880dc07996b47bf57c712bd8a and later · before c66cd500ba1a58b3798c468fcc774ed2c8c2ec7daffected · git
- 32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26b and later · before 737b80c97aef10404a9beed7c0ed45fcd5fc5931affected · git
- 8922c7940bae9ce4b1736dddb6362370793835c2 and later · before 0d7b7b31ea092e17d757bd24e2e9028ba5e3a4caaffected · git
- 91047a4396a8b1857a6f712a90cf33ec0012b189 and later · before 19e154d794eb4d33d99ca4a087b1cea9d5e65786affected · git
- 0b0e2bf39cf99e458d991b9df253727e036a7d7d and later · before 3af72bf8f73c519ee562e6963d5ff8e678924f93affected · git
- d3b739db5dc6f688a60d56da872fabaf65246032 and later · before 8460dc49c9756a1e9288218060b4d41e1b704905affected · git
- b66774b48dd98f07254951f74ea6f513efe7ff8b and later · before f49321c85785178214fd67f2e9b4b73d6363783baffected · git
- b66774b48dd98f07254951f74ea6f513efe7ff8b and later · before ca2c4c26498643f421d35ffe258fafbd3ed461c3affected · git
- 5.10.265 and later · before 5.10.273affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90091Sep 17, 2026 · Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan32Monitor
- ← EarlierCVE-2026-90092Sep 17, 2026 · Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN32Monitor
- Later →CVE-2026-90094Sep 17, 2026 · arm64: process: Fix context switching MTE store-only tag check0Monitor
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 | 0d7b7b31ea092e17d757bd24e2e9028ba5e3a4ca | Vendor (CNA) |
| Linux Linux | 19e154d794eb4d33d99ca4a087b1cea9d5e65786 | Vendor (CNA) |
| Linux Linux | 3af72bf8f73c519ee562e6963d5ff8e678924f93 | Vendor (CNA) |
| Linux Linux | 5.10.273 | Vendor (CNA) |
| Linux Linux | 5.15.224 | Vendor (CNA) |
| Linux Linux | 6.1.191 | Vendor (CNA) |
| Linux Linux | 6.12.114 | Vendor (CNA) |
| Linux Linux | 6.18.57 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | 7.2 | Vendor (CNA) |
| Linux Linux | 737b80c97aef10404a9beed7c0ed45fcd5fc5931 | Vendor (CNA) |
| Linux Linux | 8460dc49c9756a1e9288218060b4d41e1b704905 | Vendor (CNA) |
| Linux Linux | c66cd500ba1a58b3798c468fcc774ed2c8c2ec7d | Vendor (CNA) |
| Linux Linux | ca2c4c26498643f421d35ffe258fafbd3ed461c3 | Vendor (CNA) |
| Linux Linux | f49321c85785178214fd67f2e9b4b73d6363783b | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/19e154d794eb4d33d99ca4a087b1cea9d5e65786
- git.kernel.org/stable/c/3af72bf8f73c519ee562e6963d5ff8e678924f93
- git.kernel.org/stable/c/737b80c97aef10404a9beed7c0ed45fcd5fc5931
- git.kernel.org/stable/c/8460dc49c9756a1e9288218060b4d41e1b704905
- git.kernel.org/stable/c/c66cd500ba1a58b3798c468fcc774ed2c8c2ec7d
- git.kernel.org/stable/c/ca2c4c26498643f421d35ffe258fafbd3ed461c3
- git.kernel.org/stable/c/f49321c85785178214fd67f2e9b4b73d6363783b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.