High

CVE-2026-90092 — Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN New sk should not be added to parent socket accept queue after last l2cap_sock_cleanup_listen() has run in l2cap_sock_teardown_cb() and state set to BT_CLOSED, as that can result to UAF on dereferencing the dangling parent reference. l2cap_sock_new_connection_cb() may race with parent l2cap_chan teardown, due to chan->state accessed without consistent locking: [Task 1] [Task 2] l2cap_sock_release(parent) l2cap_connect l2cap_sock_shutdown pchan = l2cap_global_chan_by_psm l2cap_chan_lock(pchan) l2cap_chan_close l2cap_sock_teardown_cb pchan->state = BT_CLOSED l2cap_chan_unlock(pchan) ------> l2cap_chan_lock(pchan) l2cap_new_connection l2cap_sock_new_connection_cb l2cap_chan_lock(pchan) <-------- l2cap_chan_unlock(pchan) l2cap_sock_kill(parent) /* bt_sk(sk)->parent dangling */ Fix by adding check for sk_state == BT_LISTEN after acquiring sk lock in l2cap_sock_new_connection_cb(). Add lock_sock() around sk_state writes where missing, to avoid data races. Although the data races on pchan->state should be fixed too, this defensive sk_state check probably makes sense in any case.

Published Sep 17, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Linux

CVSS base

8.0

High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	version a2dcf1a61d056aef15b63c6eae9441344d624389version 7.1≥ 7.0.7 and < 7.1≥ 5.15.209 and < 5.16≥ 5.10.258 and < 5.11≥ 6.18.30 and < 6.18.52≥ 6.12.88 and < 6.12.110≥ 6.6.140 and < 6.6.157 and 9 more ≥ 6.1.175 and < 6.1.188≥ 0c17c8832562b2aac288e89cefd0f46074f54bcb and < bf61a65c6093970e3b50031c4b79ebf3bd411ebaversion 85426e97dc72f2088ba6d27e74cd58c3fbd43e31version 1b1c0da227bf63479bac9982fc8d12df9aaea0fb≥ 2ff1a41a912de8517b4482e946dd951b7d80edbf and < d4bfa78fd67929b62b02013c107973e0c5b7aa9a≥ 2ff1a41a912de8517b4482e946dd951b7d80edbf and < c47339e169bf4a0a4cfabb91351471f67744c2bc≥ 1810e42ff6716f320c7269d5850eca48b07b7427 and < 87276dc15b559d32757a43b4415c8445fbae06c4≥ c88c185ae0a1067823661b220aeea613df2c127b and < 2a3a27aaf19bf069720e024ce6fde54e6bf80df9≥ 5105f3e6b2df619c635b5f6a49fac131a36c7952 and < 491e4c60017969b053888029998d2a61f298986a	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Adjacent

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.0	CVSS 3.1	High	2.1	5.9	416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database
8.0	CVSS 3.1	High	—	—	Linux via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67)

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 8.0
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 17, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

6 on the record

git.kernel.org/stable/c/c47339e169bf4a0a4cfabb91351471f67744c2bc
NIST National Vulnerability Database
git.kernel.org/stable/c/d4bfa78fd67929b62b02013c107973e0c5b7aa9a
NIST National Vulnerability Database
git.kernel.org/stable/c/87276dc15b559d32757a43b4415c8445fbae06c4
NIST National Vulnerability Database
git.kernel.org/stable/c/491e4c60017969b053888029998d2a61f298986a
NIST National Vulnerability Database
git.kernel.org/stable/c/2a3a27aaf19bf069720e024ce6fde54e6bf80df9
NIST National Vulnerability Database
git.kernel.org/stable/c/bf61a65c6093970e3b50031c4b79ebf3bd411eba
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-90092 is "Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.0 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.