In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync hci_conn lookup and field access must be covered by hdev lock in set_cig_params_sync, otherwise it's possible it is freed concurrently. Take hdev lock to prevent hci_conn from being deleted or modified concurrently. Just RCU lock is not suitable here, as we also want to avoid "tearing" in the configuration.
Fix
Patch, vendor advisory and mitigation references on NVD 4
- https://git.kernel.org/stable/c/66d432e9b45bae7881ffcdb12cd8fd0bf254ef02 Patch
- https://git.kernel.org/stable/c/7d568fede8eac91161a60b710aa920abe9b0fb9f Patch
- https://git.kernel.org/stable/c/a2639a7f0f5bf7d73f337f8f077c19415c62ed2c Patch
- https://git.kernel.org/stable/c/bad65b4b0a96139f023eadc28a33125963208449 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 2
- CwesCWE-416 → CWE-416, CWE-362NVD modified 2026-10-19 20:18
- First seenCVSS 7.8 · linuxNVD modified 2026-10-16 16:17
Affected (CPE criteria) 9
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.4.16:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.5.3:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
References 5
- https://git.kernel.org/stable/c/66d432e9b45bae7881ffcdb12cd8fd0bf254ef02 Patch
- https://git.kernel.org/stable/c/7502c1cf303b69f71d085f5ff7251b0e1b0f09df
- https://git.kernel.org/stable/c/7d568fede8eac91161a60b710aa920abe9b0fb9f Patch
- https://git.kernel.org/stable/c/a2639a7f0f5bf7d73f337f8f077c19415c62ed2c Patch
- https://git.kernel.org/stable/c/bad65b4b0a96139f023eadc28a33125963208449 Patch