{ "schema_version": "1.6.1", "id": "RPI-CVE-2023-53520", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2023-53520" ], "published": "2025-10-01T11:50:00Z", "summary": "Bluetooth: Fix hci_suspend_sync crash", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Fix hci_suspend_sync crash\n\nIf hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier\nmay still be accessing it, it can cause the program to crash.\nHere's the call trace:\n <4>[102152.653246] Call Trace:\n <4>[102152.653254] hci_suspend_sync+0x109/0x301 [bluetooth]\n <4>[102152.653259] hci_suspend_dev+0x78/0xcd [bluetooth]\n <4>[102152.653263] hci_suspend_notifier+0x42/0x7a [bluetooth]\n <4>[102152.653268] notifier_call_chain+0x43/0x6b\n <4>[102152.653271] __blocking_notifier_call_chain+0x48/0x69\n <4>[102152.653273] __pm_notifier_call_chain+0x22/0x39\n <4>[102152.653276] pm_suspend+0x287/0x57c\n <4>[102152.653278] state_store+0xae/0xe5\n <4>[102152.653281] kernfs_fop_write+0x109/0x173\n <4>[102152.653284] __vfs_write+0x16f/0x1a2\n <4>[102152.653287] ? selinux_file_permission+0xca/0x16f\n <4>[102152.653289] ? security_file_permission+0x36/0x109\n <4>[102152.653291] vfs_write+0x114/0x21d\n <4>[102152.653293] __x64_sys_write+0x7b/0xdb\n <4>[102152.653296] do_syscall_64+0x59/0x194\n <4>[102152.653299] entry_SYSCALL_64_after_hwframe+0x5c/0xc1\n\nThis patch holds the reference count of the hci_dev object while\nprocessing it in hci_suspend_notifier to avoid potential crash\ncaused by the race condition.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.1.21-1+rpt1", "1:6.1.47-1+rpt2", "1:6.1.47-1+rpt4", "1:6.1.54-1+rpt2" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.1.0-rpi1-rpi-v6", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi1-rpi-v7", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi1-rpi-v7l", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi1-rpi-v8", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v6", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v7", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v7l", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v8", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-2712", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v6", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v8", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-2712", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-v6", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-v7", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-v7l", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-v8", "binary_version": "1:6.1.54-1+rpt2" } ] }, "database_specific": { "per_version": { "1:6.1.21-1+rpt1": { "linux_commit": "0afb5e98488aed7017b9bf321b575d0177feb7ed", "upstream_version": "6.1.21", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.55" }, "1:6.1.47-1+rpt2": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.55" }, "1:6.1.47-1+rpt4": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.55", "compiled_filter": false }, "1:6.1.54-1+rpt2": { "linux_commit": "2906f7abdc03d4a92b6b0e2e0c87ea2a9dffe8f7", "upstream_version": "6.1.54", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.55" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2023-53520" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/e1fa25a91091bbed691ba2996a6cee809e3309a2" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/06e2b5ad72b60f90bfe565c201346532e271f484" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/f9c8ce5d665653e3cf71a76349d41d7a7f7947e6" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/573ebae162111063eedc6c838a659ba628f66a0f" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-05T11:24:39Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 7.8, "cvss_v3_severity": "High", "scenario": "AV:L - The vulnerable callback is only invoked from the kernel PM notifier chain (system suspend/resume initiated via /sys/power/state, logind, or lid/button events) racing with local HCI device unregistration; there is no over-the-air or network path that reaches hci_suspend_notifier, so the attack must be staged from local system access.\nAC:L - An attacker who can initiate suspend/resume and cause the Bluetooth adapter to unregister (e.g. adding/removing a USB Bluetooth dongle on a shared workstation or kiosk) drives both sides of the race and can retry the suspend/unplug cycle indefinitely until the window is hit.\nPR:L - On typical desktop, laptop and kiosk deployments an unprivileged user in an active local session can request suspend through logind/polkit, and adapter unregistration can be induced without root, so basic local user privileges suffice rather than real root.\nUI:N - The attacker performs both the suspend request and the adapter removal themselves; no action by a separate victim user is needed to reach the racing code paths.\nS:U - The freed hci_dev object and the corrupted memory both live in the kernel's own security authority; exploitation yields kernel-level compromise without crossing a VM, IOMMU or sandbox boundary.\nC:H - Use-after-free of the kzalloc'd hci_dev structure lets an attacker reclaim the slab object and have hci_suspend_sync()/hci_resume_sync() read attacker-influenced or stale kernel data, providing a path to arbitrary kernel memory disclosure.\nI:H - The stale hdev is written to (hdev->suspended, suspend_state, scanning_paused) and its function pointers (hdev->send, hdev->wakeup) and workqueue/mutex members are dereferenced after free, giving heap-spray-based arbitrary write and control-flow hijack potential.\nA:H - The reported failure mode is an outright kernel crash during suspend (hci_suspend_sync oops), and any UAF of this kind reliably panics or hangs the system, denying service across a suspend/resume cycle." } } }