SECUFOCUSNOW
Home›Remediation guides›CVE-2025-39982
CVE REMEDIATION GUIDE
Review reviewHighResearch in progress

CVE-2025-39982 remediation guide

Linux

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync This fixes the following UFA in hci_acl_create_conn_sync where a connection still pending is command submission (conn->state == BT_OPEN) maybe freed, also since this also can happen with the likes of hci_le_create_conn_sync fix it as well: BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5ef/0x790 net/bluetooth/hci_sync.c:6861 Write of size 2 at addr ffff88805ffcc038 by task kworker/u11:2/9541 CPU: 1 UID: 0 PID: 9541 Comm: kworker/u11:2 Not tainted 6.16....

Open CVE record
Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductLinux
Affected versions>= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < 6243bda271a628c48875e3e473206e7f584892ce, >= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < bcce99f613163a43de24674b717e7a6c135fc879, >= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < 484c7d571a3d1b3fd298fa691b660438c4548a53, >= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < a78fd4fc5694ecb3b97deb2ad9eaebd67b4d2b08, >= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < 9e622804d57e2d08f0271200606bd1270f75126f, >= 5.18
Fixed versionsNo verified fixed-version field is available yet
Priority basisReview · CVSS 8.8 · EPSS 0.26%
01

Identify the affected asset

Confirm whether Linux 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.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < 6243bda271a628c48875e3e473206e7f584892ce, >= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < bcce99f613163a43de24674b717e7a6c135fc879, >= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < 484c7d571a3d1b3fd298fa691b660438c4548a53, >= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < a78fd4fc5694ecb3b97deb2ad9eaebd67b4d2b08, >= aef2aa4fa98e18ea5d9345bf777ee698c8598728 < 9e622804d57e2d08f0271200606bd1270f75126f, >= 5.18. Treat incomplete inventory results as unresolved.

03

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.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: No verified fixed-version field is available yet. Preserve configuration and rollback material before change.

05

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.