CVE-2025-38117 remediation guide
Linux Linux, linux kernel
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Protect mgmt_pending list with its own lock This uses a mutex to protect from concurrent access of mgmt_pending list which can cause crashes like: ================================================================== BUG: KASAN: slab-use-after-free in hci_sock_get_channel+0x60/0x68 net/bluetooth/hci_sock.c:91 Read of size 2 at addr ffff0000c48885b2 by task syz.4.334/7318 CPU: 0 UID: 0 PID: 7318 Comm: syz.4.334 Not tainted 6.15.0-rc7-syzkaller-g187899f4124a #0 PREEMPT Hardware name: Google Google Compute Engine...
Identify the affected asset
Confirm whether Linux Linux, linux kernel is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= a380b6cff1a2d2139772e88219d08330f84d0381 < bdd56875c6926d8009914f427df71797693e90d4, >= a380b6cff1a2d2139772e88219d08330f84d0381 < 4e83f2dbb2bf677e614109df24426c4dded472d4, >= a380b6cff1a2d2139772e88219d08330f84d0381 < d7882db79135c829a922daf3571f33ea1e056ae3, >= a380b6cff1a2d2139772e88219d08330f84d0381 < 6fe26f694c824b8a4dbf50c635bee1302e3f099c, >= 4.1, >= 4.1 < 6.6.94, >= 6.7 < 6.12.34, >= 6.13 < 6.15.3, 6.16. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 6.6.94, 6.12.34, 6.15.3. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.