Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53358: Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()

Noroxi assessment

Priority: Monitor (action score 35/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.28% (FIRST EPSS).
  • Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3634cbdc2eb414b69ffa752ddbe5e0458518e321, 50dfec218808b148ab4247b1858031b7a32015c5, 7555fd885a0603f50e49a655850a1f2bd8a25398.

Low priority for now. Upgrade to Linux Linux 3634cbdc2eb414b69ffa752ddbe5e0458518e321, 50dfec218808b148ab4247b1858031b7a32015c5, 7555fd885a0603f50e49a655850a1f2bd8a25398 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: use chan timer to close channels in cleanup_listen() l2cap_chan_close() removes the channel from conn->chan_l, which must be done under conn->lock. cleanup_listen() runs under the parent sk_lock, so acquiring conn->lock would invert the established conn->lock -> chan->lock -> sk_lock order. Instead of calling l2cap_chan_close() directly, schedule l2cap_chan_timeout with delay 0 to close the channel asynchronously. The timeout handler already acquires conn->lock and chan->lock in the correct order. The timer is only armed when chan->conn is still set: if it is already NULL, l2cap_conn_del() has already processed this channel (l2cap_chan_del + l2cap_sock_teardown_cb + l2cap_sock_close_cb), so there is nothing left to do. If l2cap_conn_del() races in after the timer is armed, __clear_chan_timer() inside l2cap_chan_del() cancels it; if the timer has already fired, the handler returns harmlessly because chan->conn was cleared.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Jul 2, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 20th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
8.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.

Follow CVE-2026-53358

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

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • 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 (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.

Running WordPress? Scan your site free with WP Lens

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.4 and later · before 5.10.259
  • linux linux kernel5.11 and later · before 5.15.210
  • linux linux kernel5.16 and later · before 6.1.176
  • linux linux kernel6.2 and later · before 6.6.143
  • linux linux kernel6.7 and later · before 6.12.93
  • linux linux kernel6.13 and later · before 6.18.35
  • linux linux kernel6.19 and later · before 7.0.12
  • linux linux kernel7.1

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

    • 3.4affected
    • 3df91ea20e744344100b10ae69a17211fcf5b207 and later · before 3634cbdc2eb414b69ffa752ddbe5e0458518e321affected · git
    • 3df91ea20e744344100b10ae69a17211fcf5b207 and later · before e1c100e2d61bd8c718b7d91fe3e050780a9bf72daffected · git
    • 3df91ea20e744344100b10ae69a17211fcf5b207 and later · before deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9affected · git
    • 3df91ea20e744344100b10ae69a17211fcf5b207 and later · before 89dec92041717b027216e110599e4f6d6c921b79affected · git
    • 3df91ea20e744344100b10ae69a17211fcf5b207 and later · before 50dfec218808b148ab4247b1858031b7a32015c5affected · git
    • 3df91ea20e744344100b10ae69a17211fcf5b207 and later · before 859d3ace791ed878ae9ba5522c7844d960da8f88affected · git
    • 3df91ea20e744344100b10ae69a17211fcf5b207 and later · before 7555fd885a0603f50e49a655850a1f2bd8a25398affected · git
    • 3df91ea20e744344100b10ae69a17211fcf5b207 and later · before 8c8e620467a7b51562dbcefbd1f09f288d7d710daffected · git
    • before 3.4not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 7.0.12-17.0.12-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53356Jul 1, 2026 · drm/i915/gem: Fix phys BO pread/pwrite with offset
    31Monitor
  • ← EarlierCVE-2026-53357Jul 2, 2026 · Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del()
    32Monitor
  • Later →CVE-2026-53359Jul 4, 2026 · KVM: x86: Fix shadow paging use-after-free due to unexpected role
    35Monitor

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 Linux3634cbdc2eb414b69ffa752ddbe5e0458518e321Vendor (CNA)
Linux Linux50dfec218808b148ab4247b1858031b7a32015c5Vendor (CNA)
Linux Linux7555fd885a0603f50e49a655850a1f2bd8a25398Vendor (CNA)
Linux Linux859d3ace791ed878ae9ba5522c7844d960da8f88Vendor (CNA)
Linux Linux89dec92041717b027216e110599e4f6d6c921b79Vendor (CNA)
Linux Linux8c8e620467a7b51562dbcefbd1f09f288d7d710dVendor (CNA)
Linux Linuxdeb8493a8fa599f6c95e2465b12bfdfb7f94a1d9Vendor (CNA)
Linux Linuxe1c100e2d61bd8c718b7d91fe3e050780a9bf72dVendor (CNA)
debian:linux6.12.94-1 · Debian:13Package 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).

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.

Finders, 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 on the same network segment can trigger it.
  • No account or password is required.
  • 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
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/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.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records