SECUFOCUSNOW
Home›CVE index›CVE-2025-39981
Review reviewHigh

CVE-2025-39981

Linux

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix possible UAFs This attemps to fix possible UAFs caused by struct mgmt_pending being freed while still being processed like in the following trace, in order to fix mgmt_pending_valid is introduce and use to check if the mgmt_pending hasn't been removed from the pending list, on the complete callbacks it is used to check and in addtion remove the cmd from the list while holding mgmt_pending_lock to avoid TOCTOU problems since if the cmd is left on the list it can still be accessed and freed. BUG: KASAN: s...

CVSS
7.8
EPSS
0.14%
3.76% percentile
CISA KEV
Not listed
Published
2025.10.15
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix possible UAFs This attemps to fix possible UAFs caused by struct mgmt_pending being freed while still being processed like in the following trace, in order to fix mgmt_pending_valid is introduce and use to check if the mgmt_pending hasn't been removed from the pending list, on the complete callbacks it is used to check and in addtion remove the cmd from the list while holding mgmt_pending_lock to avoid TOCTOU problems since if the cmd is left on the list it can still be accessed and freed. BUG: KASAN: s...

Affected product and versions

Product
Linux
Affected versions
>= cf75ad8b41d2aa06f98f365d42a3ae8b059daddd < 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a, >= cf75ad8b41d2aa06f98f365d42a3ae8b059daddd < d71b98f253b079cbadc83266383f26fe7e9e103b, >= cf75ad8b41d2aa06f98f365d42a3ae8b059daddd < 87a1f16f07c6c43771754075e08f45b41d237421, >= cf75ad8b41d2aa06f98f365d42a3ae8b059daddd < 302a1f674c00dd5581ab8e493ef44767c5101aab, >= 5.17
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available