CVE-2026-90256

High

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via hci_conn_timeout (disc_work) -> hci_proto_disconn_ind -> l2cap_disconn_ind. This is UAF if the l2cap_conn is deleted concurrently. disc_work is disabled sync in hci_conn_del(), so we cannot take hci_dev_lock in disc_work. Fix by using proto_lock to guard l2cap_data, in addition to hdev->lock which is held in other access paths.

Package Linux Kernel
Published 2026-09-17
Last modified 2026-09-18
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

8.8

out of 10
High
Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Vector string
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.6.84, 6.12.20, 6.13.8, 6.14 and later are affected. Fixed in 7.2.6, 7.3-rc1 and their respective stable series.

Affected from
≥ 6.6.84 ≥ 6.12.20 ≥ 6.13.8 ≥ 6.14
Fixed in
✓ 7.2.6 7.2.x ✓ 7.3-rc1

Frequently asked questions

  • What is CVE-2026-90256?

    CVE-2026-90256 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10 . It affects Linux kernel versions from 6.6.84 onward and has been patched in 7.2.6 and 7.3-rc1. CVE-2026-90256 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2026-90256?

    CVE-2026-90256 has a CVSS score of 8.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H .

  • Is there a patch available for CVE-2026-90256?

    Yes. CVE-2026-90256 has been patched. Fixed versions include 7.2.6 and 7.3-rc1. If you are running Linux kernel 6.6.84 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-90256 actively exploited?

    No. CVE-2026-90256 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.