CVE-2025-39981: Bluetooth: MGMT: Fix possible UAFs
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a, 302a1f674c00dd5581ab8e493ef44767c5101aab, 87a1f16f07c6c43771754075e08f45b41d237421; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
Low priority for now. Upgrade to Linux Linux 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a, 302a1f674c00dd5581ab8e493ef44767c5101aab, 87a1f16f07c6c43771754075e08f45b41d237421; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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: slab-use-after-free in mgmt_add_adv_patterns_monitor_sync+0x35/0x50 net/bluetooth/mgmt.c:5223 Read of size 8 at addr ffff8880709d4dc0 by task kworker/u11:0/55 CPU: 0 UID: 0 PID: 55 Comm: kworker/u11:0 Not tainted 6.16.4 #2 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 Workqueue: hci0 hci_cmd_sync_work Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 mgmt_add_adv_patterns_monitor_sync+0x35/0x50 net/bluetooth/mgmt.c:5223 hci_cmd_sync_work+0x210/0x3a0 net/bluetooth/hci_sync.c:332 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x711/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16.4/arch/x86/entry/entry_64.S:245 </TASK> Allocated by task 12210: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __kmalloc_cache_noprof+0x230/0x3d0 mm/slub.c:4364 kmalloc_noprof include/linux/slab.h:905 [inline] kzalloc_noprof include/linux/slab.h:1039 [inline] mgmt_pending_new+0x65/0x1e0 net/bluetooth/mgmt_util.c:269 mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296 __add_adv_patterns_monitor+0x130/0x200 net/bluetooth/mgmt.c:5247 add_adv_patterns_monitor+0x214/0x360 net/bluetooth/mgmt.c:5364 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:729 sock_write_iter+0x258/0x330 net/socket.c:1133 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x5c9/0xb30 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 12221: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:576 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x62/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2381 [inline] slab_free mm/slub.c:4648 [inline] kfree+0x18e/0x440 mm/slub.c:4847 mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline] mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257 __mgmt_power_off+0x169/0x350 net/bluetooth/mgmt.c:9444 hci_dev_close_sync+0x754/0x1330 net/bluetooth/hci_sync.c:5290 hci_dev_do_close net/bluetooth/hci_core.c:501 [inline] hci_dev_close+0x108/0x200 net/bluetooth/hci_core.c:526 sock_do_ioctl+0xd9/0x300 net/socket.c:1192 sock_ioctl+0x576/0x790 net/socket.c:1313 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf ---truncated---
- Published
- Oct 15, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.17affected
- cf75ad8b41d2aa06f98f365d42a3ae8b059daddd and later · before 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9aaffected · git
- cf75ad8b41d2aa06f98f365d42a3ae8b059daddd and later · before d71b98f253b079cbadc83266383f26fe7e9e103baffected · git
- cf75ad8b41d2aa06f98f365d42a3ae8b059daddd and later · before 87a1f16f07c6c43771754075e08f45b41d237421affected · git
- cf75ad8b41d2aa06f98f365d42a3ae8b059daddd and later · before 302a1f674c00dd5581ab8e493ef44767c5101aabaffected · git
- before 5.17not affected · semver
- 6.6.140 and later · up to and including 6.6.*not affected · semver
- 6.12.59 and later · up to and including 6.12.*not affected · semver
- 6.16.10 and later · up to and including 6.16.*not affected · semver
- 6.17 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-124.20.1.el10_1 | 6.12.0-124.20.1.el10_1 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-124.20.1.el10_1 | 6.12.0-124.20.1.el10_1 |
| AlmaLinux:8 | bpftool | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.126.1.el8_10 | 4.18.0-553.126.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.126.1.rt7.467.el8_10 | 4.18.0-553.126.1.rt7.467.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.126.1.rt7.467.el8_10 | 4.18.0-553.126.1.rt7.467.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.126.1.rt7.467.el8_10 | 4.18.0-553.126.1.rt7.467.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.126.1.rt7.467.el8_10 | 4.18.0-553.126.1.rt7.467.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.126.1.rt7.467.el8_10 | 4.18.0-553.126.1.rt7.467.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.126.1.rt7.467.el8_10 | 4.18.0-553.126.1.rt7.467.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.126.1.rt7.467.el8_10 | 4.18.0-553.126.1.rt7.467.el8_10 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-39979Oct 15, 2025 · net/mlx5: fs, fix UAF in flow counter release31Monitor
- ← EarlierCVE-2025-39980Oct 15, 2025 · nexthop: Forbid FDB status change while nexthop is in a group0Monitor
- Later →CVE-2025-39982Oct 15, 2025 · Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a | Vendor (CNA) |
| Linux Linux | 302a1f674c00dd5581ab8e493ef44767c5101aab | Vendor (CNA) |
| Linux Linux | 87a1f16f07c6c43771754075e08f45b41d237421 | Vendor (CNA) |
| Linux Linux | d71b98f253b079cbadc83266383f26fe7e9e103b | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.141.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-611.11.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.63-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-611.11.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+2
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.