Skip to main content

Linux Kernel EUVDEUVD-2026-38721

| CVE-2026-52918 HIGH
2026-06-24 Linux GHSA-rf7j-4mgx-52c3
8.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Timing-dependent local race on Bluetooth sockets needs local access and a won race, so AV:L/AC:H/PR:L; UAF can yield kernel memory corruption (C/I/A:H).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
7.1 HIGH
AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jun 28, 2026 - 08:22 vuln.today
CVSS changed
Jun 28, 2026 - 08:22 NVD
8.8 (HIGH)
Patch available
Jun 24, 2026 - 09:16 EUVD
CVE Published
Jun 24, 2026 - 07:14 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 24, 2026 - 07:14 cve.org
HIGH 8.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: serialize accept_q access

bt_sock_poll() walks the accept queue without synchronization, while child teardown can unlink the same socket and drop its last reference. The unsynchronized accept queue walk has existed since the initial Bluetooth import.

Protect accept_q with a dedicated lock for queue updates and polling. Also rework bt_accept_dequeue() to take temporary child references under the queue lock before dropping it and locking the child socket.

AnalysisAI

Use-after-free in the Linux kernel Bluetooth subsystem allows a crafted sequence of socket polling and connection teardown to dereference a freed sock structure, because bt_sock_poll() walks the per-socket accept queue without synchronization while a concurrent child teardown unlinks the same socket and drops its last reference. The flaw has existed since the original Bluetooth import and affects effectively all kernel versions until the fixed stable releases; EPSS is low (0.18%, 7th percentile) and there is no public exploit identified at time of analysis. Successful exploitation of the freed-object access can corrupt kernel memory, enabling denial of service and potentially privilege escalation.

Technical ContextAI

The defect lives in the Bluetooth L2CAP/RFCOMM socket layer (net/bluetooth/af_bluetooth.c), specifically the bt_sock accept-queue (accept_q) handling. When a Bluetooth listening socket accepts incoming connections, child sockets are queued onto accept_q. bt_sock_poll() iterates this list to report readiness, but did so with no lock, while bt_accept_dequeue() and child teardown can concurrently unlink a child and release its final reference. The result is a classic race-condition-induced use-after-free (CWE-362 leading to CWE-416); the CWE is reported as N/A in the source feed but the description and fix (introducing a dedicated queue lock and taking temporary child references under that lock before dropping it) make the root cause unambiguous. The CPE strings (cpe:2.3:a:linux:linux:*) are wildcard/version-agnostic and do not narrow affected builds, so the EUVD/stable git ranges must be used for precise version scoping.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 5.10.259, 5.15.210, 6.1.176, 6.6.142, 6.12.92, 6.18.34, or mainline 7.1 (or later) - matching your maintained branch; the fix adds a dedicated lock serializing accept_q updates and polling and takes temporary child references before locking the child socket (see the git.kernel.org/stable/c/ commits, e.g. d9ce4de05df2 and 41c8c1c7923e). Apply your distribution's corresponding patched kernel package, since most enterprises consume backported stable fixes rather than building mainline. If immediate patching is not possible, the most direct compensating control is to reduce exposure of the vulnerable code path: disable or unload the Bluetooth stack (e.g. blacklist the bluetooth/bnep/rfcomm/l2cap modules or disable the Bluetooth service) on systems that do not require it, which fully removes the attack surface at the cost of losing Bluetooth functionality; on systems that need Bluetooth, restrict which local users/processes can open Bluetooth sockets and avoid running untrusted local code, since the race requires concurrent local socket operations. Advisory references: https://nvd.nist.gov/vuln/detail/CVE-2026-52918 and https://vuldb.com/vuln/373156.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.168 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.149 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.197 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.145 Affected
Container suse/sle-micro-rancher/5.3:latest Container suse/sle-micro-rancher/5.4:5.4.4.5.149 Affected
Container suse/sle-micro/base-5.5:2.0.4-5.8.296 Affected
Container suse/sle-micro/kvm-5.5:2.0.4-3.5.570 Affected

Share

EUVD-2026-38721 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy