BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-39981High confidence

Bluetooth: MGMT: Fix possible UAFs

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 21 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.63-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-39981 · CSAF 2.0 · revision 51 · interimSUSE Product Security TeamCVE-2025-39981
15 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
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: 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 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---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-34591

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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---

What

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---

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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---

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-2298Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Daten zu manipulieren und andere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251022Security Bulletin 22 Oct 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Oct 2025, published on 22 October 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0986Multiples vulnérabilités dans les produits IBM

27 Bulletin de sécurité IBM 7282829 du 07 août 2026 https://www.ibm.com/support/pages/node/7282829 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2024-34459 https://www.cve.org/CVERecord?id=CVE-2024-34459 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2025-13755 https://www.cve.org/CVERecord?id=CVE-2025-13755 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-36372 https://www.cve.org/CVERecord?id=CVE-2025-36372 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-53906 https://www.cve.org/CVERecord?id=CVE-2025-53906 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2025-68183 https://www.cve.org/CVERecord?id=CVE-2025-68183 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2026-10025 https://www.cve.org/CVERecord?id=CVE-2026-10025 Référence CVE CVE-2026-10109 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0665Multiples vulnérabilités dans le noyau Linux de Red Hat

ur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Red Hat RHSA-2026:21209 du 27 mai 2026 https://access.redhat.com/errata/RHSA-2026:21209 Bulletin de sécurité Red Hat RHSA-2026:21706 du 28 mai 2026 https://access.redhat.com/errata/RHSA-2026:21706 Bulletin de sécurité Red Hat RHSA-2026:21745 du 28 mai 2026 https://access.redhat.com/errata/RHSA-2026:21745 Référence CVE CVE-2025-21999 https://www.cve.org/CVERecord?id=CVE-2025-21999 Référence CVE CVE-2025-38653 https://www.cve.org/CVERecord?id=CVE-2025-38653 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-68183 https://www.cve.org/CVERecord?id=CVE-2025-68183 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68741 https://www.cve.org/CVERecord?id=CVE-2025-68741 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2026-23243 https://www.cve.org/CVERecord?id=CVE-2026-23243 Référence CVE CVE-2026-23270 https://www.cve.org/CVERecord?id=CVE-2026-23270 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0602Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39991 https://www.cve.org/CVERecord?id=CVE-2025-39991 Référence CVE CVE-2025-39992 https://www.cve.org/CVERecord?id=CVE-2025-39992 Référence CVE CVE-2025-39994 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0496Multiples vulnérabilités dans le noyau Linux de Red Hat

du 22 avril 2026 https://access.redhat.com/errata/RHSA-2026:9836 Bulletin de sécurité Red Hat RHSA-2026:9870 du 22 avril 2026 https://access.redhat.com/errata/RHSA-2026:9870 Référence CVE CVE-2022-50053 https://www.cve.org/CVERecord?id=CVE-2022-50053 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38180 https://www.cve.org/CVERecord?id=CVE-2025-38180 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-68741 https://www.cve.org/CVERecord?id=CVE-2025-68741 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2026-23001 https://www.cve.org/CVERecord?id=CVE-2026-23001 Référence CVE CVE-2026-23066 https://www.cve.org/CVERecord?id=CVE-2026-23066 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0421Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39991 https://www.cve.org/CVERecord?id=CVE-2025-39991 Référence CVE CVE-2025-39992 https://www.cve.org/CVERecord?id=CVE-2025-39992 Référence CVE CVE-2025-39994 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0397Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39991 https://www.cve.org/CVERecord?id=CVE-2025-39991 Référence CVE CVE-2025-39992 https://www.cve.org/CVERecord?id=CVE-2025-39992 Référence CVE CVE-2025-39994 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0371Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39991 https://www.cve.org/CVERecord?id=CVE-2025-39991 Référence CVE CVE-2025-39992 https://www.cve.org/CVERecord?id=CVE-2025-39992 Référence CVE CVE-2025-39994 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0331Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39991 https://www.cve.org/CVERecord?id=CVE-2025-39991 Référence CVE CVE-2025-39992 https://www.cve.org/CVERecord?id=CVE-2025-39992 Référence CVE CVE-2025-39994 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0056Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2025-39825 Référence CVE CVE-2025-39840 https://www.cve.org/CVERecord?id=CVE-2025-39840 Référence CVE CVE-2025-39843 https://www.cve.org/CVERecord?id=CVE-2025-39843 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39898 https://www.cve.org/CVERecord?id=CVE-2025-39898 Référence CVE CVE-2025-39905 https://www.cve.org/CVERecord?id=CVE-2025-39905 Référence CVE CVE-2025-39925 https://www.cve.org/CVERecord?id=CVE-2025-39925 Référence CVE CVE-2025-39966 https://www.cve.org/CVERecord?id=CVE-2025-39966 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39983 https://www.cve.org/CVERecord?id=CVE-2025-39983 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=CVE-2025-39993 Référence CVE CVE-2025-40141 https://www.cve.org/CVERecord?id=CVE-2025-40141 Référence CVE CVE-2025-40176 https://www.cve.org/CVERecord?id=CVE-2025-40176 Référence CVE CVE-2025-40240 https://www.cve.org/CVERecord?id=CVE-2025-40240 Référence CVE CVE-2025-40277 https://www.cve.org/CVERecord?id=CVE-2025-40277 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0017Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2025-38729 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39843 https://www.cve.org/CVERecord?id=CVE-2025-39843 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39925 https://www.cve.org/CVERecord?id=CVE-2025-39925 Référence CVE CVE-2025-39955 https://www.cve.org/CVERecord?id=CVE-2025-39955 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39983 https://www.cve.org/CVERecord?id=CVE-2025-39983 Référence CVE CVE-2025-40186 https://www.cve.org/CVERecord?id=CVE-2025-40186 Référence CVE CVE-2025-40300 https://www.cve.org/CVERecord?id=CVE-2025-40300 Gestion détaillée du document le 09 janvier 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1105Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2023-53401 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38737 https://www.cve.org/CVERecord?id=CVE-2025-38737 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39925 https://www.cve.org/CVERecord?id=CVE-2025-39925 Référence CVE CVE-2025-39966 https://www.cve.org/CVERecord?id=CVE-2025-39966 Référence CVE CVE-2025-39979 https://www.cve.org/CVERecord?id=CVE-2025-39979 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39983 https://www.cve.org/CVERecord?id=CVE-2025-39983 Référence CVE CVE-2025-40047 https://www.cve.org/CVERecord?id=CVE-2025-40047 Référence CVE CVE-2025-40058 https://www.cve.org/CVERecord?id=CVE-2025-40058 Référence CVE CVE-2025-40185 https://www.cve.org/CVERecord?id=CVE-2025-40185 Gestion détaillée du document le 12 décembre 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.go

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1074Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2025-39751 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39864 https://www.cve.org/CVERecord?id=CVE-2025-39864 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39898 https://www.cve.org/CVERecord?id=CVE-2025-39898 Référence CVE CVE-2025-39918 https://www.cve.org/CVERecord?id=CVE-2025-39918 Référence CVE CVE-2025-39955 https://www.cve.org/CVERecord?id=CVE-2025-39955 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-40058 https://www.cve.org/CVERecord?id=CVE-2025-40058 Référence CVE CVE-2025-40185 https://www.cve.org/CVERecord?id=CVE-2025-40185 Référence CVE CVE-2025-40186 https://www.cve.org/CVERecord?id=CVE-2025-40186 Gestion détaillée du document le 05 décembre 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité de

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1073Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39979 https://www.cve.org/CVERecord?id=CVE-2025-39979 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39984 https://www.cve.org/CVERecord?id=CVE-2025-39984 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39991 https://www.cve.org/CVERecord?id=CVE-2025-39991 Référence CVE CVE-2025-39992 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1047Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-39965 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39991 https://www.cve.org/CVERecord?id=CVE-2025-39991 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=CVE-2025-39993 Référence CVE CVE-2025-39994 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1032Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-39965 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39984 https://www.cve.org/CVERecord?id=CVE-2025-39984 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39991 https://www.cve.org/CVERecord?id=CVE-2025-39991 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-39965 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39984 https://www.cve.org/CVERecord?id=CVE-2025-39984 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39991 https://www.cve.org/CVERecord?id=CVE-2025-39991 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0899Multiples vulnérabilités dans les produits Microsoft

CVE-2022-49069 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39967 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39968 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39969 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39970 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39971 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39972 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39973 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39977 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39980 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39981 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39982 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39985 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39987 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39990 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39994 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39998 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49124 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49133 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-49568 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-53687

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 15 Oct 2025 · Last source change 5 Aug 2026, 12:06 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-34591
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-39981 · cve.blacktree.nl