{ "schema_version": "1.6.1", "id": "RPI-CVE-2024-42132", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2024-42132" ], "published": "2024-07-30T07:47:52Z", "summary": "bluetooth/hci: disallow setting handle bigger than HCI_CONN_HANDLE_MAX", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbluetooth/hci: disallow setting handle bigger than HCI_CONN_HANDLE_MAX\n\nSyzbot hit warning in hci_conn_del() caused by freeing handle that was\nnot allocated using ida allocator.\n\nThis is caused by handle bigger than HCI_CONN_HANDLE_MAX passed by\nhci_le_big_sync_established_evt(), which makes code think it's unset\nconnection.\n\nAdd same check for handle upper bound as in hci_conn_set_handle() to\nprevent warning.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.6.20-1+rpt1", "1:6.6.28-1+rpt1", "1:6.6.31-1+rpt1" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.6.20+rpt-rpi-2712", "binary_version": "1:6.6.20-1+rpt1" }, { "binary_name": "linux-image-6.6.20+rpt-rpi-v6", "binary_version": "1:6.6.20-1+rpt1" }, { "binary_name": "linux-image-6.6.20+rpt-rpi-v7", "binary_version": "1:6.6.20-1+rpt1" }, { "binary_name": "linux-image-6.6.20+rpt-rpi-v7l", "binary_version": "1:6.6.20-1+rpt1" }, { "binary_name": "linux-image-6.6.20+rpt-rpi-v8", "binary_version": "1:6.6.20-1+rpt1" }, { "binary_name": "linux-image-6.6.28+rpt-rpi-2712", "binary_version": "1:6.6.28-1+rpt1" }, { "binary_name": "linux-image-6.6.28+rpt-rpi-v6", "binary_version": "1:6.6.28-1+rpt1" }, { "binary_name": "linux-image-6.6.28+rpt-rpi-v7", "binary_version": "1:6.6.28-1+rpt1" }, { "binary_name": "linux-image-6.6.28+rpt-rpi-v7l", "binary_version": "1:6.6.28-1+rpt1" }, { "binary_name": "linux-image-6.6.28+rpt-rpi-v8", "binary_version": "1:6.6.28-1+rpt1" }, { "binary_name": "linux-image-6.6.31+rpt-rpi-2712", "binary_version": "1:6.6.31-1+rpt1" }, { "binary_name": "linux-image-6.6.31+rpt-rpi-v6", "binary_version": "1:6.6.31-1+rpt1" }, { "binary_name": "linux-image-6.6.31+rpt-rpi-v7", "binary_version": "1:6.6.31-1+rpt1" }, { "binary_name": "linux-image-6.6.31+rpt-rpi-v7l", "binary_version": "1:6.6.31-1+rpt1" }, { "binary_name": "linux-image-6.6.31+rpt-rpi-v8", "binary_version": "1:6.6.31-1+rpt1" } ] }, "database_specific": { "per_version": { "1:6.6.20-1+rpt1": { "linux_commit": "6f16847710cc0502450788b9f12f0a14d3429668", "upstream_version": "6.6.20", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.6.39" }, "1:6.6.28-1+rpt1": { "linux_commit": "0c341f47adc3578cd5f817aa20ee2b7f9ae6b23e", "upstream_version": "6.6.28", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.6.39" }, "1:6.6.31-1+rpt1": { "linux_commit": "c1432b4bae5b6582f4d32ba381459f33c34d1424", "upstream_version": "6.6.31", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.6.39" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2024-42132" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/2ae8d7742a09c275872e670c53337b3dcedaa11c" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/4970e48f83dbd21d2a6a7cdaaafc2a71f7f45dc4" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/d311036696fed778301d08a71a4bef737b86d8c5" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/1cc18c2ab2e8c54c355ea7c0423a636e415a0c23" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-05T11:52:36Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 7.6, "cvss_v3_severity": "High", "scenario": "AV:A - The vulnerable code is the Bluetooth HCI event path (`hci_le_cis_req_evt`/`hci_le_big_sync_established_evt`), driven by LE CIS requests and BIG sync establishment initiated by a remote peer in radio range. Per Bluetooth scoring convention this is Adjacent.\nAC:L - No race, no memory-layout grooming, and no timing dependency \u2014 a single HCI event carrying a connection handle above 0x0eff deterministically creates a bogus \"unset\" hci_conn whose teardown always hits the ida_free WARN.\nPR:N - LE ACL connections and broadcast/PA sync require no pairing, bonding, or authentication, and no local account is needed; the attacker only needs to be an unauthenticated peer in range of a host with LE Audio/ISO enabled.\nUI:N - The event handlers run automatically in `hci_rx_work` as part of normal LE connection and broadcast-sync processing; no victim action is required.\nS:U - The corruption is confined to the kernel's own Bluetooth connection and IDA state within the same security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:L - The `WARN(1, ...)` in `ida_free()` emits a full register and stack backtrace containing kernel text and heap addresses, giving a bounded KASLR-defeating info leak; there is no arbitrary read primitive.\nI:L - The erroneous `ida_free()` desynchronizes `hdev->unset_handle_ida`, releasing an ID still owned by another connection so the same handle can be issued twice and `hci_conn_hash_lookup_handle()` resolves to the wrong connection; the out-of-range handle also corrupts the PB/BC flag bits of outgoing ACL/ISO headers. This is bounded kernel-state modification, not an arbitrary write.\nA:H - The bug reliably triggers a kernel WARNING, which is a panic on the many deployments (Android, CI, hardened distros) running with `panic_on_warn`, and the resulting duplicate-handle confusion persistently disrupts Bluetooth connection handling." } } }