CVE-2026-90091Hinoki check available

Adjacent kernel crash via L2CAP cleanup race

Published Sep 17, 2026 · Updated Sep 18, 2026

Race condition in Linux Bluetooth L2CAP socket cleanup allows adjacent authenticated users to crash the kernel via concurrent teardown. l2cap_sock_cleanup_listen() reads l2cap_pi(sk)->chan without synchronization while l2cap_sock_kill() can clear it, producing a null-pointer dereference. Reachability requires low-privileged adjacent access to trigger the competing L2CAP teardown paths; the bounded consequence is a kernel crash.

CVSS severity8.0
High
EPSS probability0.35%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Race condition in Linux Bluetooth L2CAP socket cleanup allows adjacent authenticated users to crash the kernel via concurrent teardown. l2cap_sock_cleanup_listen() reads l2cap_pi(sk)->chan without synchronization while l2cap_sock_kill() can clear it, producing a null-pointer dereference. Reachability requires low-privileged adjacent access to trigger the competing L2CAP teardown paths; the bounded consequence is a kernel crash.

The record

CVE
CVE-2026-90091
Published
Sep 17, 2026
Updated
Sep 18, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499.004
Attack vector
adjacent
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=36da806f7fbaee56ad9e81859deec203f9728700 <61d5ddbd524c715b224cbe7e9f01da4e05098b19
  2. Affected versionversion=6.1.178 <6.1.188
  3. Affected versionversion=6.12.97 <6.12.110
  4. Affected versionversion=6.18.40 <6.18.52
  5. Affected versionversion=6.6.145 <6.6.157
  6. Affected versionversion=6fef032af0092ed5ccb767239a9ac1bc38c08a40 <32a7bc6e93be36b37fe61f351d312d358195bd61
  7. Affected versionversion=6fef032af0092ed5ccb767239a9ac1bc38c08a40 <66d6ef18548ae6d7dd452b84115fc82c0a73a4ea
  8. Affected versionversion=7.1.5 <7.2
  9. Affected versionversion=7.2
  10. Affected versionversion=733e76e74e406c1d1ddc7369420dd8a47f48bb8a
  11. Affected versionversion=84e718b6a814edc84159361f9f454a4e92ae91ae <4f8c63fe0097c9f6ea34409f82f79b3894903d91
  12. Affected versionversion=8c37e4338c801ebb8cee52436c01c41e009f6e87 <7c7ac736b50fa259ed1bdddc18d79523f07c0442
  13. Affected versionversion=b39298044e5534612511a2ff5de03ba5f6e7a820 <827de6bd2865b22aaabd554540def3b8a33018ab

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=36da806f7fbaee56ad9e81859deec203f9728700 <61d5ddbd524c715b224cbe7e9f01da4e05098b19; version=6.1.178 <6.1.188; version=6.12.97 <6.12.110; version=6.18.40 <6.18.52; version=6.6.145 <6.6.157; version=6fef032af0092ed5ccb767239a9ac1bc38c08a40 <32a7bc6e93be36b37fe61f351d312d358195bd61; version=6fef032af0092ed5ccb767239a9ac1bc38c08a40 <66d6ef18548ae6d7dd452b84115fc82c0a73a4ea; version=7.1.5 <7.2; version=7.2; version=733e76e74e406c1d1ddc7369420dd8a47f48bb8a; version=84e718b6a814edc84159361f9f454a4e92ae91ae <4f8c63fe0097c9f6ea34409f82f79b3894903d91; version=8c37e4338c801ebb8cee52436c01c41e009f6e87 <7c7ac736b50fa259ed1bdddc18d79523f07c0442; version=b39298044e5534612511a2ff5de03ba5f6e7a820 <827de6bd2865b22aaabd554540def3b8a33018ab

Published CVSS scores

8.0OSVCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started