Skip to main content

Linux Kernel CVE-2026-64128

| EUVDEUVD-2026-45813 MEDIUM
NULL Pointer Dereference (CWE-476)
2026-07-19 Linux GHSA-qwwx-92m3-hf86
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
6.5 MEDIUM

BIS allows any proximate wireless broadcaster to trigger the crash without authentication, making AV:A/PR:N more accurate than the assigned AV:L/PR:L; availability impact is high (kernel panic), with no confidentiality or integrity impact.

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

Primary rating from NVD.

CVSS VectorNVD

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

Lifecycle Timeline

5
Analysis Generated
Aug 13, 2026 - 15:29 vuln.today
CVSS changed
Aug 13, 2026 - 15:22 NVD
5.5 (MEDIUM)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:40 nvd
MEDIUM 5.5
CVE Published
Jul 19, 2026 - 15:40 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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

Bluetooth: ISO: drop ISO_END frames received without prior ISO_START

ISO data PDUs carry a packet-boundary flag indicating START, CONT, END or SINGLE. The ISO_CONT branch of iso_recv() guards against a missing ISO_START by checking conn->rx_len before touching conn->rx_skb, but ISO_END does not.

If a peer sends an ISO_END as the first packet on a fresh ISO connection, conn->rx_skb is still NULL and conn->rx_len is zero, so skb_put(conn->rx_skb, ...) dereferences NULL and oopses. For BIS, where receivers sync to a broadcaster without pairing, any broadcaster on the air can trigger this.

Mirror the ISO_CONT check at the top of ISO_END so a stray end fragment is logged and dropped instead of crashing the host.

AnalysisAI

Null pointer dereference in the Linux kernel's Bluetooth ISO reassembly path allows any Bluetooth broadcaster within radio range to crash a victim Linux host by transmitting an ISO_END PDU without a preceding ISO_START on a BIS (Broadcast Isochronous Stream) connection. Affected kernels span all stable branches from the ISO introduction commit (ccf74f2390d60a2f9a75ef496d2564abb478f46a) through fixed releases 6.1.175, 6.6.142, 6.12.92, 6.18.34, 7.0.11, and 7.1. No public exploit code or CISA KEV listing exists at time of analysis; EPSS is 0.18% (8th percentile), reflecting low current exploitation probability despite the unauthenticated wireless trigger available to BIS attackers.

Technical ContextAI

The vulnerability resides in the Linux kernel Bluetooth ISO layer (net/bluetooth/iso.c), which implements Isochronous Channels introduced with Bluetooth LE Audio (Bluetooth 5.2+). ISO PDUs carry a packet-boundary flag encoding one of four states: ISO_START, ISO_CONT, ISO_END, or SINGLE. The iso_recv() reassembly function guards the ISO_CONT branch by checking conn->rx_len before touching conn->rx_skb, preventing use of an uninitialized socket buffer - but the ISO_END branch lacks this same guard. CWE-476 (NULL Pointer Dereference) is triggered because conn->rx_skb remains NULL when no ISO_START has yet arrived; the unconditional skb_put(conn->rx_skb, ...) in the ISO_END path then dereferences that NULL pointer and panics the kernel. BIS (Broadcast Isochronous Stream) is particularly exposed: BIS receivers synchronize to broadcasters without pairing or connection establishment, so no trust or authentication relationship is required before a peer can deliver ISO PDUs. The CPE cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* confirms the affected product is the mainline Linux kernel across all architectures that support Bluetooth ISO.

RemediationAI

The primary fix is to upgrade to a patched stable kernel release appropriate for the deployed branch: 6.1.175, 6.6.142, 6.12.92, 6.18.34, 7.0.11, or 7.1. Upstream fix commits are available at https://git.kernel.org/stable/c/1c3d1e1696b72579b970e17999c503a14535205b and the five related stable commits. Ubuntu users should apply packages described in USN-8593-1 at https://ubuntu.com/security/notices/USN-8593-1. If immediate patching is not feasible, a compensating control for BIS-exposed systems is to unload the Bluetooth kernel module (modprobe -r bluetooth), which eliminates the attack surface entirely at the cost of disabling all Bluetooth functionality on the host. A narrower alternative is to prevent Bluetooth ISO socket creation via a custom seccomp or LSM policy restricting BTPROTO_ISO socket calls - this disables LE Audio without affecting classic Bluetooth, though it requires kernel LSM support and careful policy authoring. Systems not using Bluetooth LE Audio features are not exposed even with the module loaded, since the vulnerable code path requires an active ISO or BIS sync attempt.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-64128 vulnerability details – vuln.today

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