Links submitted by the Threat Radar community and AI curated for defenders.

Community Curated

CVE Database V5

AlienVault OTX General

Real-world exploitation and exposure telemetry from the OffSeq Mirage honeypot fleet and Sonar internet scans — which CVEs attackers are actually exploiting and which are exposed in the wild, plus attacker IoCs. All IPs are masked; no raw victim or sensor identity is ever published.

OffSeq Mirage

Bleeping Computer

SANS ISC Handlers Diary

SecurityWeek

Threatpost

Reddit ExploitDev

Latest exploits, shellcode, and vulnerability proofs-of-concept from Exploit-DB

Exploit-DB RSS Feed

Reddit ThreatIntel

Reddit BlueTeam

Reddit Reverse Engineering

Reddit Malware

Reddit Cybersecurity

Reddit NetSec

ThreatFox MISP Feed

CIRCL OSINT Feed

NCSC UK

JVN Japan

GCP Compute Engine Security

GCP Kubernetes Security

AWS Security Bulletins

CERT/CC

Tenable Research

Google Project Zero

Microsoft Security Blog

Cisco Talos

Zero Day Initiative

Palo Alto Unit 42

Krebs on Security

Kaspersky Security Blog

Check Point Research

GCVE Database

Reddit InfoSec News

The Hacker News

Dark Reading

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

A high-severity vulnerability in the Linux kernel's Bluetooth L2CAP implementation was resolved by changing how channels are closed in cleanup_listen(). The fix avoids lock order inversion by scheduling channel closure asynchronously via a timer handler that acquires locks in the correct order. This prevents potential race conditions and improper channel cleanup.

The vulnerability in the Linux kernel Bluetooth L2CAP subsystem involved improper locking order when closing channels in cleanup_listen(). Directly calling l2cap_chan_close() under the parent sk_lock would invert the established lock order (conn->lock -> chan->lock -> sk_lock), risking race conditions or deadlocks. The fix schedules l2cap_chan_timeout with zero delay to close channels asynchronously, ensuring locks are acquired in the correct order. The timer is only armed if chan->conn is set, and if the channel is already processed or races occur, the timer is safely canceled or the handler exits harmlessly.

Detailed information about GHSA-g5v6-wm74-gh57. Get real-time updates, technical details, and mitigation strategies.

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()… (CVE-2026-53358) - Live Threat Intelligence - Threat Radar | OffSeq.com

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()… (CVE-2026-53358)

linux

linux-aws

linux-azure

linux-lts-xenial

linux-aws-hwe

linux-gcp

linux-hwe

linux-hwe-edge

linux-kvm

linux-oracle

linux-fips

linux-aws-5.0

linux-aws-5.3

linux-aws-5.4

linux-azure-4.15

linux-azure-5.3

linux-azure-5.4

linux-azure-edge

linux-gcp-4.15

linux-gcp-5.3

linux-gcp-5.4

linux-gke-4.15

linux-gke-5.4

linux-gkeop-5.4

linux-hwe-5.4

linux-ibm-5.4

linux-oem

linux-oracle-5.0

linux-oracle-5.3

linux-oracle-5.4

linux-raspi-5.4

linux-aws-fips

linux-azure-fips

linux-gcp-fips

linux-aws-5.11

linux-aws-5.13

linux-aws-5.15

linux-aws-5.8

linux-azure-5.11

linux-azure-5.13

linux-azure-5.15

linux-azure-5.8

linux-azure-fde

linux-azure-fde-5.15

linux-bluefield

linux-gcp-5.11

linux-gcp-5.13

linux-gcp-5.15

linux-gcp-5.8

linux-gke

linux-gke-5.15

linux-gkeop

linux-gkeop-5.15

linux-hwe-5.11

linux-hwe-5.13

linux-hwe-5.15

linux-hwe-5.8

linux-ibm

linux-ibm-5.15

linux-intel-5.13

linux-intel-iotg-5.15

linux-iot

linux-lowlatency-hwe-5.15

linux-nvidia-tegra-5.15

linux-oem-5.10

linux-oem-5.13

linux-oem-5.14

linux-oem-5.6

linux-oracle-5.11

linux-oracle-5.13

linux-oracle-5.15

linux-oracle-5.8

linux-raspi

linux-raspi2

linux-riscv

linux-riscv-5.11

linux-riscv-5.15

A vulnerability in the Linux kernel Bluetooth L2CAP subsystem was resolved by changing the channel closing mechanism in cleanup_listen() to use an asynchronous timer handler. This avoids lock order inversion issues by scheduling l2cap_chan_timeout with delay 0 instead of directly calling l2cap_chan_close(). The vulnerability affects multiple Linux kernel versions prior to 7.0.0-28.28 and related builds. A patch is available and included in recent Ubuntu kernel updates.

The Linux kernel Bluetooth L2CAP subsystem had a vulnerability related to improper lock handling during channel closure in cleanup_listen(). The function l2cap_chan_close() removes channels under conn->lock, but cleanup_listen() runs under sk_lock, and acquiring conn->lock there would invert the expected lock order (conn->lock -> chan->lock -> sk_lock). To fix this, the channel closure is deferred asynchronously by scheduling l2cap_chan_timeout with zero delay, which acquires locks in the correct order. The timer is only armed if chan->conn is set, preventing race conditions with l2cap_conn_del(). This fix prevents potential concurrency issues in Bluetooth channel cleanup.

Detailed information about UBUNTU-CVE-2026-53358 affecting null linux. Get real-time updates, technical details, and mitigation strategies.

UBUNTU-CVE-2026-53358 - Live Threat Intelligence - Threat Radar | OffSeq.com


In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()… (CVE-2026-53358)CVE-2026-53358 0 A high-severity vulnerability in the Linux kernel's Bluetooth L2CAP implementation was resolved by changing how channels are closed in cleanup_listen(). The fix avoids lock order inversion by scheduling channel closure asynchronously via a timer handler that acquires locks in the correct order. This prevents potential race conditions and improper channel cleanup. HighVulnerability#gcve #osv #ghsa-g5v6-wm74-gh57 Join the discussion	GCVE Database	07/02/2026, 15:32:12 UTC Added: 07/02/2026, 22:57:28 UTC
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()… (CVE-2026-53358)CVE-2026-53358 0 A vulnerability in the Linux kernel Bluetooth L2CAP subsystem was resolved by changing the channel closing mechanism in cleanup_listen() to use an asynchronous timer handler. This avoids lock order inversion issues by scheduling l2cap_chan_timeout with delay 0 instead of directly calling l2cap_chan_close(). The vulnerability affects multiple Linux kernel versions prior to 7.0.0-28.28 and related builds. A patch is available and included in recent Ubuntu kernel updates. MediumVulnerability#gcve #osv #ubuntu-cve-2026-53358 Join the discussion	GCVE Database	07/02/2026, 15:17:00 UTC Added: 07/17/2026, 10:15:04 UTC

Threats Tagged 'cve-2026-53358'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'cve-2026-53358'

Lead Pen Test Professional