cve.bz

CVE-2026-74539 linux linux

8.0 highEPSS 0.2%Fix available

High (8.0) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: lock sk in iso_sock_getname Accessing iso_pi(sk)->conn requires lock_sock, which is not held here. Fix by adding the lock/release.

Severity

CVSS 3.1

8.0 high
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-74539 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74539?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74539?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-74539 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.16 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.44
Linux7.17.1.8
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.1.8-1DEBIAN-CVE-2026-74539
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-74539
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-74539
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-74539
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-74539
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-74539 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-74539 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-74539 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-74539 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-74539 USN-9020-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 27 moreno fix listedUBUNTU-CVE-2026-74539
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-74539
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-74539 USN-8959-1
12 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquitastreamlinux-lts6.18.46-r0BELL-CVE-2026-74539

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Bluetooth ISO iso_sock_getname accessed iso_pi(sk) connection state without holding the socket lock even though iso_pi(sk) conn requires lock_sock protection. A local process operating an AF_BLUETOOTH ISO socket could race getpeername() or getsockname() with connection teardown or state changes, potentially leading to a stale connection pointer dereference, kernel crash, or use-after-free behavior. For the CVSS the PR:L is used because a local process must be able to operate an AF_BLUETOOTH ISO socket and trigger the local socket API path. The issue is not directly network reachable through IP networking. Bluetooth peer activity may influence connection state timing, but reliable triggering still depends on the local socket operation. Impact is at least local denial of service via kernel crash.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-74539.

References

Check your stackJSON