{ "schema_version": "1.6.1", "id": "RPI-CVE-2026-74539", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2026-74539" ], "published": "2026-08-15T12:28:42Z", "summary": "Bluetooth: ISO: lock sk in iso_sock_getname", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: lock sk in iso_sock_getname\n\nAccessing iso_pi(sk)->conn requires lock_sock, which is not held here.\n\nFix by adding the lock/release.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:13", "name": "linux" }, "versions": [ "1:6.18.29-1+rpt1", "1:6.18.33-1+rpt1", "1:6.18.34-1+rpt1", "1:6.18.39-1+rpt1" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.18.29+rpt-rpi-2712", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v6", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v7", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-2712", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v6", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v7", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-2712", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v6", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v7", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-2712", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v6", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v7", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8-rt", "binary_version": "1:6.18.39-1+rpt1" } ] }, "database_specific": { "per_version": { "1:6.18.29-1+rpt1": { "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc", "upstream_version": "6.18.29", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.44" }, "1:6.18.33-1+rpt1": { "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412", "upstream_version": "6.18.33", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.44" }, "1:6.18.34-1+rpt1": { "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af", "upstream_version": "6.18.34", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.44" }, "1:6.18.39-1+rpt1": { "linux_commit": "60ea684a8ace97bb0db1a16e20753bdd6ab371ff", "upstream_version": "6.18.39", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.44" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2026-74539" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/72d5bb1d77d7c3330146dc0cfd43f704c64b9594" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/202670e6602e068558c1fca2df40719ee91a2906" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/89cf154d7c18e6e94a3da83051f3cf2bac317ae2" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-17T05:50:24Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 8.0, "cvss_v3_severity": "High", "scenario": "AV:A - The unlocked `iso_sock_getname()` path is entered only via the local `getpeername()` syscall, but the freeing side races through `iso_conn_del()`/`iso_chan_del()` driven by HCI connect/disconnect events that an adjacent Bluetooth peer can time (CIS/BIS/PA teardown on LE Audio phones, headsets, or kiosks).\nAC:L - An attacker controls both race sides: one thread loops `getpeername()` on a `BTPROTO_ISO` socket while another concurrently calls `close()`/`connect()` or an adjacent peer provokes HCI disconnect; unlimited retries make winning the TOCTOU on `iso_pi(sk)->conn` reliably achievable.\nPR:L - `iso_sock_create()`/`bt_sock_create()` impose no `CAP_NET_ADMIN` or other capability check; any unprivileged local user in the initial network namespace who can open `AF_BLUETOOTH`/`BTPROTO_ISO` sockets can reach the vulnerable `getpeername()` handler (Bluetooth is unavailable in user namespaces).\nUI:N - Exploitation requires only attacker-controlled ISO socket syscalls and concurrent connection teardown; no victim pairing prompt, mount, or other deliberate user action beyond normal Bluetooth LE Audio use on an already-configured device.\nS:U - Impact is kernel heap UAF/crash or privilege escalation within the host kernel security boundary; it does not cross VM, hypervisor, IOMMU, or application-sandbox boundaries.\nC:H - The double-read `iso_pi(sk)->conn ? iso_pi(sk)->conn->hcon` without `lock_sock` is a classic TOCTOU UAF; dereferencing a freed `iso_conn` and stale `hcon` exposes attacker-influenced kernel heap contents and is leverageable for arbitrary memory disclosure.\nI:H - UAF on the `iso_conn` kmalloc object (~136-byte slab) enables heap grooming/spray; corrupted `hcon` pointers and subsequent kernel reads through attacker-controlled freed memory provide write primitives chainable to control-flow hijack per kernel UAF scoring guidance.\nA:H - Racing `iso_chan_del()` during the unlocked `conn->hcon` dereference or `hcon->type` access can cause immediate kernel oops/panic from NULL/invalid pointer access; UAF in connection teardown independently threatens host availability even before full exploitation." } } }