The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Bluetooth: hci_core: Fix use-after-free in vhci_flush() syzbot reported use-after-free in vhci_flush()     without repro. [0] From the splat, a thread close()d a vhci file descriptor while its device was being     used by iotcl() on another thread. Once the last fd refcnt is released, vhci_release() calls     hci_unregister_dev(), hci_free_dev(), and kfree() for struct vhci_data, which is set to     hci_dev->dev->driver_data. The problem is that there is no synchronisation after unlinking hdev from     hci_dev_list in hci_unregister_dev(). There might be another thread still accessing the hdev which was     fetched before the unlink operation. We can use SRCU for such synchronisation. Let's run hci_dev_reset()     under SRCU and wait for its completion in hci_unregister_dev(). Another option would be to restore     hci_dev->destruct(), which was removed in commit 587ae086f6e4 (Bluetooth: Remove unused hci-destruct     cb). However, this would not be a good solution, as we should not run hci_unregister_dev() while there     are in-flight ioctl() requests, which could lead to another data-race KCSAN splat. Note that other drivers     seem to have the same problem, for exmaple, virtbt_remove(). [0]: BUG: KASAN: slab-use-after-free in     skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline] BUG: KASAN: slab-use-after-free in     skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937 Read of size 8 at addr ffff88807cb8d858 by task     syz.1.219/6718 CPU: 1 UID: 0 PID: 6718 Comm: syz.1.219 Not tainted     6.16.0-rc1-syzkaller-00196-g08207f42d3ff #0 PREEMPT(full) Hardware name: Google Google Compute     Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: <TASK> dump_stack_lvl+0x189/0x250     lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xd2/0x2b0     mm/kasan/report.c:521 kasan_report+0x118/0x150 mm/kasan/report.c:634 skb_queue_empty_lockless     include/linux/skbuff.h:1891 [inline] skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937     skb_queue_purge include/linux/skbuff.h:3368 [inline] vhci_flush+0x44/0x50 drivers/bluetooth/hci_vhci.c:69     hci_dev_do_reset net/bluetooth/hci_core.c:552 [inline] hci_dev_reset+0x420/0x5c0     net/bluetooth/hci_core.c:592 sock_do_ioctl+0xd9/0x300 net/socket.c:1190 sock_ioctl+0x576/0x790     net/socket.c:1311 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+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP:
    0033:0x7fcf5b98e929 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48     89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89     01 48 RSP: 002b:00007fcf5c7b9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX:
    00007fcf5bbb6160 RCX: 00007fcf5b98e929 RDX: 0000000000000000 RSI: 00000000400448cb RDI: 0000000000000009     RBP: 00007fcf5ba10b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11:
    0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fcf5bbb6160 R15: 00007ffd6353d528     </TASK> Allocated by task 6535: 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:4359 kmalloc_noprof include/linux/slab.h:905 [inline] kzalloc_noprof include/linux/slab.h:1039     [inline] vhci_open+0x57/0x360 drivers/bluetooth/hci_vhci.c:635 misc_open+0x2bc/0x330     drivers/char/misc.c:161 chrdev_open+0x4c9/0x5e0 fs/char_dev.c:414 do_dentry_open+0xdf0/0x1970     fs/open.c:964 vfs_open+0x3b/0x340 fs/open.c:1094 do_open fs/namei.c:3887 [inline]     path_openat+0x2ee5/0x3830 fs/name ---truncated--- (CVE-2025-38250)

Note that Nessus relies on the presence of the package as reported by the vendor.

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - Bluetoothhci_corevhci_flush() での use-after-free を修正します syzbot は repro なしで vhci_flush() での use-after-free を報告しました。 [0] スプラットから、デバイスが別のスレッドの iotcl() によって使用されている間に、スレッド close()da vhci ファイル記述子。最後の fd refcnt がリリースされると、vhci_release() は、hci_dev->dev->driver_data に設定された struct vhci_data に対して hci_unregister_dev()、hci_free_dev()、および kfree() を呼び出します。問題は、hci_unregister_dev() で hci_dev_list から hdev をリンク解除した後に同期が存在しないことです。リンク解除操作の前にフェッチされた hdev にまだアクセス中の別のスレッドが存在する可能性があります。このような同期には SRCU を使用できます。SRCU で hci_dev_reset() を実行し、hci_unregister_dev() で完了するまで待機します。別のオプションは、hci_dev->destruct() を復元することです。これは、コミット 587ae086f6e4 で削除されていますBluetooth: 使用されていない hci-destruct cb を削除します。ただし、インフライト中の ioctl() リクエストがある間は hci_unregister_dev() を実行すべきではないため、これは良い解決策とはなりません。これにより、別のデータ競合の KCSAN スプラットが発生する可能性があります。注意virtbt_remove() などの、他のドライバーにも同じ問題があるようです。 [0]バグ KASANskb_queue_empty_lockless の slab-use-after-free include/linux/skbuff.h:1891 [インライン] バグ KASANskb_queue_purge_reason+0x99/0x360 net/core/ の slab-use-after-free skbuff.c:3937 タスク syz.1.219/6718 による addr ffff88807cb8d858 でのサイズ 8 の読み取り CPU1 UID0 PID6718 通信syz.1.219 汚染されていない 6.16.0-rc1-syzkaller-00196-g08207f42d3ff #0 PREEMPT()完全) ハードウェア名: Google Google Compute Engine/Google Compute Engine、BIOS Google 05/07/2025 呼び出しトレース <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [インライン] ] print_report+0xd2/0x2b0 mm/kasan/report.c:521 kasan_report+0x118/0x150 mm/kasan/report.c:634 skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline] skb_queue_purge_reason+0x99/0x360 net/core /skbuff.c:3937 skb_queue_purge include/linux/skbuff.h:3368 [inline] vhci_flush+0x44/0x50 drivers/bluetooth/hci_vhci.c:69 hci_dev_do_reset net/bluetooth/hci_core.c:552 [inline] hci_dev_reset+0x420/ 0x5c0 net/bluetooth/hci_core.c :592 sock_do_ioctl+0xd9/0x300 net/socket.c:1190 sock_ioctl+0x576/0x790 net/socket.c:1311 vfs_ioctl fs/ioctl.c:51 [インライン] __do_sys_ioctl fs/ioctl.c:907 [インライン]
    __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 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/
    0033:0x7fcf5b98e929 コード: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 0640 <48> [c840440] 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff f7 d8 64 89 01 48 RSP
    00007fcf5bbb6160 RCX: 00007fcf5b98e929 RDX: 0000000000000000 RSI: 00000000400448cb RDI: 0000000000000009 RBP: 00007fcf5ba10b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11:
     R120000000000000246  : 0000000000000000 R13: 0000000000000000 R14: 00007fcf5bbb6160 R15: 00007ffd6353d528 </TASK> Allocated by task 6535: 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:4359 kmalloc_noprof include/linux/slab.h:905 [インライン] kzalloc_noprof include/linux/slab.h:1039 [インライン] vhci_open+0x57/0x360 ドライバー/bluetooth/hci_vhci.c:635 misc_open+0x2bc/0x330 ドライバー/ char/misc.c:161 chrdev_open+0x4c9/0x5e0 fs/char_dev.c:414 do_dentry_open+0xdf0/0x1970 fs/open.c:964 vfs_open+0x3b/0x340 fs/open.c:1094 do_open fs/namei.c 3887 [インライン] path_openat+0x2ee5/0x3830 fs/name ---truncated---CVE-2025-38250]

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - Bluetoothhci_core修复 vhci_flush() 中的释放后使用 syzbot 报告在 vhci_flush() 中无重现的释放后使用。 [0] 从 splat 可以发现当另一个线程上的 iotcl() 使用其设备时线程 close()da vhci 文件描述符。释放最后一个 fd refcnt 后vhci_release() 会调用 vhci_data 结构的 hci_unregister_dev()、hci_free_dev() 和 kfree()其被设置为 hci_dev->dev->driver_data。问题是在取消 hdev 与 hci_unregister_dev() 中的 hci_dev_list 的链接之后并无同步。可能有另一个线程仍在访问在取消链接操作之前提取的 hdev。我们可以使用 SRCU 进行此类同步。让我们在 SRCU 下运行 hci_dev_reset() 并在 hci_unregister_dev() 中等待其完成。另一个选项是还原 hci_dev->destruct()其已在提交 587ae086f6e4蓝牙删除未使用的 hci-destruct cb中删除。但是这不是一个好的解决方案因为存在处理中的 ioctl() 请求时我们不应运行 hci_unregister_dev()这样可导致另一个数据争用 KCSAN splat。请注意其他驱动程序似乎也存在相同的问题例如 virtbt_remove()。 [0]BUGKASANskb_queue_empty_lockless include/linux/skbuff.h:1891 [inline] BUGKASANskb_queue_purge_reason+0x99/0x360 net/core/ 中存在 slab-use-after-free skbuff.c:3937 由任务 syz.1.219/6718 CPU:1 UID:0 PID:6718 Comm:syz.1.219 未受感染 6.16.0-rc1-syzkaller-00196-g08207f42d3ff #0 PREEMPT(完整) 硬件名称Google Google Compute Engine/Google Compute EngineBIOS Google 05/07/2025 调用跟踪 <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [内联] print_report+0xd2/0x2b0 mm/kasan/report.c:521 kasan_report+0x118/0x150 mm/kasan/report.c:634 skb_queue_empty_lockless include/linux/skbuff.h:1891 [内联] skb_queue_purge_reason+0x99/0x360 net/core /skbuff.c:3937 skb_queue_purge include/linux/skbuff.h:3368 [内联] vhci_flush+0x44/0x50 drivers/bluetooth/hci_vhci.c:69 hci_dev_do_reset net/bluetooth/hci_core.c:552 [内联] hci_dev_reset+0x420/ 0x5c0 net/bluetooth/hci_core.c :592 sock_do_ioctl+0xd9/0x300 net/socket.c:1190 sock_ioctl+0x576/0x790 net/socket.c:1311 vfs_ioctl fs/ioctl.c:51 [内联] __do_sys_ioctl fs/ioctl.c:907 [内联]
    __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [内联] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP
    0033:0x7fcf5b98e929 代码ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 04c <48> [2f d0 4c ] 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP002b:00007fcf5c7b9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX
    00007fcf5bbb6160 RCX: 00007fcf5b98e929 RDX: 0000000000000000 RSI: 00000000400448cb RDI: 0000000000000009 RBP: 00007fcf5ba10b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11:
     R120000000000000246  : 0000000000000000 R13: 0000000000000000 R14: 00007fcf5bbb6160 R15: 00007ffd6353d528 </TASK> Allocated by task 6535: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c: 68poison_kmalloc_redzone mm/kasan/common.c:377 [内联] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [内联] __kmalloc_cache_noprof+0x230/0x3d0 mm/slub。 c:4359 kmalloc_noprof include/linux/slab.h:905 [内联] kzalloc_noprof include/linux/slab.h:1039 [内联] vhci_open+0x57/0x360 drivers/bluetooth/hci_vhci.c:635 misc_open+0x2bc/0x330 drivers/ char/misc.c:161 chrdev_open+0x4c9/0x5e0 fs/char_dev.c:414 do_dentry_open+0xdf0/0x1970 fs/open.c:964 vfs_open+0x3b/0x340 fs/open.c:1094 do_open fs/namei.c 3887 [inline] path_openat+0x2ee5/0x3830 fs/name ---truncated--- (CVE-2025-38250)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - 藍牙hci_core修正 vhci_flush() 中的釋放後使用 syzbot 在 vhci_flush() 中報告無重現的釋放後使用。 [0] 在其他執行緒上的 iotcl() 使用其裝置時執行緒會在 splat 中關閉 ()da vhci 檔案描述符號。一旦釋放最後一個 fd refcntvhci_release() 就會針對設為 hci_dev->dev->driver_data 的 vhci_data 結構呼叫 hci_unregister_dev()、hci_free_dev() 和 kfree()。問題是在 hci_unregister_dev() 中從 hci_dev_list 取消連結 hdev 後沒有同步處理。可能有其他執行緒仍在存取在取消連結作業前擷取的 hdev。我們可以使用 SRCU 來進行這種同步處理。我們在 SRCU 底下執行 hci_dev_reset()並等待其在 hci_unregister_dev() 中完成。另一個選項是還原 hci_dev->destruct()其已在認可 587ae086f6e4 中移除 (藍牙移除未使用的 hci-destruct cb)。不過這並不是一個好的解決方案因為我們不應在 ioctl() 要求執行期間執行 hci_unregister_dev()而這可導致另一個資料爭用 KCSAN 展開。請注意其他驅動程式似乎有相同問題例如virtbt_remove()。 [0]BUGKASANskb_queue_empty_lockless include/linux/skbuff.h:1891 中的 slab 釋放後使用 [內嵌] 錯誤 KASANskb_queue_purge_reason+0x99/0x360 net/core/ 中的 slab 釋放後使用skbuff.c:3937 工作 syz.1.219/6718 CPU 在 addr ffff88807cb8d858 讀取大小為 8 CPU1 UID0 PID 6718 通訊 syz.1.219 未受污染的 6.16.0-rc1-syzkaller-00196-g08207f42d3ff #0 PREEMPT(完整) 硬體名稱Google Google Compute Engine/Google Compute Engine、BIOS Google 05/07/2025 呼叫追踪 <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [內嵌] print_report+0xd2/0x2b0 mm/kasan/report.c:521 kasan_report+0x118/0x150 mm/kasan/report.c:634 skb_queue_empty_lockless include/linux/skbuff.h:1891 [內嵌] skb_queue_purge_reason+0x99/0x360 net/core /skbuff.c:3937 skb_queue_purge include/linux/skbuff.h:3368 [內嵌] vhci_flush+0x44/0x50 drivers/bluetooth/hci_vhci.c:69 hci_dev_do_reset net/bluetooth/hci_core.c:552 [內嵌] hci_dev_reset+0x420/ 0x5c0 net/bluetooth/hci_core.c :592 sock_do_ioctl+0xd9/0x300 net/socket.c:1190 sock_ioctl+0x576/0x790 net/socket.c:1311 vfs_ioctl fs/ioctl.c:51 [內嵌] __do_sys_ioctl fs/ioctl.c:907 [內嵌]
    __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [內嵌] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP:
    [0033:0x7fcf5b98e929 程式碼ff ff c3 66 2e 0f 1f 84 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c 4 8 4c 8b 0c 5c 5 <48> 5 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP002b:00007fcf5c7b9038 EFLAGS00000246 ORIG_RAX0000000000000010 RAXffffffffffffffda RBX
    00007fcf5bbb6160 RCX: 00007fcf5b98e929 RDX: 0000000000000000 RSI: 00000000400448cb RDI: 0000000000000009 RBP: 00007fcf5ba10b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11:
     R120000000000000246  : 0000000000000000 R13: 0000000000000000 R14: 00007fcf5bbb6160 R15: 00007ffd6353d528 </TASK> Allocated by task 6535: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c: 68 pox_kmalloc_redzone mm/kasan/common.c:377 [內嵌] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [內嵌] __kmalloc_cache_noprof+0x230/0x3d0 mm/slub。 c:4359 kmalloc_noprof include/linux/slab.h:905 [內嵌] kzalloc_noprof include/linux/slab.h:1039 [內嵌] vhci_open+0x57/0x360 drivers/bluetooth/hci_vhci.c:635 misc_open+0x2bc/0x330 drivers/ char/misc.c:161 chrdev_open+0x4c9/0x5e0 fs/char_dev.c:414 do_dentry_open+0xdf0/0x1970 fs/open.c:964 vfs_open+0x3b/0x340 fs/open.c:1094 do_open fs/namei.c: 3887 [內嵌] path_openat+0x2ee5/0x3830 fs/name ---truncated--- (CVE-2025-38250)

請注意，Nessus 依賴供應商報告的套件存在。

ID	Name	Product	Family	Published	Updated	Severity
246087	Linux Distros Unpatched Vulnerability : CVE-2025-38250	Nessus	Misc.	8/8/2025	8/8/2025	high
246087	Linux Distros のパッチ未適用の脆弱性: CVE-2025-38250	Nessus	Misc.	8/8/2025	8/8/2025	high
246087	Linux Distros 未修补的漏洞：CVE-2025-38250	Nessus	Misc.	8/8/2025	8/8/2025	high
246087	Linux Distros 未修補的弱點：CVE-2025-38250	Nessus	Misc.	8/8/2025	8/8/2025	high

Detections

Analytics

Plugins Search

high

high

high

high