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

  - hfs__hfs_bnode_create での hfs_bnode_get() の欠落を修正します。Syzbot は、hfs_bnode_put() でカーネルバグを発見しました
    fs/hfs/bnode.c:466! におけるカーネルバグ無効な opcode: 0000#1] PREEMPT SMP KASAN CPU: 0 PID: 3634 Comm:
    kworker/u4:5 汚染されていない 6.1.0-rc7-syzkaller-00190-g97ee9d1c1696 #0 ハードウェア名Google Google Compute Engine/Google Compute Engine、BIOS Google 10/26/2022 ワークキューwriteback wb_workfnflush-7:0 RIP
    0010:hfs_bnode_put+0x46f/0x480 fs/hfs/bnode.c:466 コード8a 80 ff e9 73 fe ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c a0 fe ff ff 48 89 df e8 db 8a 80 ff e9 93 fe ff ff e8 a1 68 2c ff <0f> 0b e8 9a 68 2c ff 0f 0b 0f 1f 84 00 00 00 00 00 55 41 57 41 56 RSP 0018 :ffffc90003b4f258 EFLAGS : 00010293 RAX : 20010293 RAX
    0000000000000000 RCX: ffff8880739dd7c0 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc90003b4f430 R08: ffffffff825e2d9b R09: ffffed10045157d1 R10: ffffed10045157d1 R11:
     R121ffff110045157d0  : ffff8880228abe80 R13: ffff88807016c000 R14: dffffc0000000000 R15: ffff8880228abe00 FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fa6ebe88718 CR3: 000000001e93d000 CR400000000003506f0 DR0
    0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> hfs_write_inode+0x1bc/0xb40 write_inode fs/fs-writeback.c:1440 [inline] __writeback_single_inode+0x4d6/0x670 fs/fs-writeback. c:1652 writeback_sb_inodes+0xb3b/0x18f0 fs/fs-writeback.c:1878 __writeback_inodes_wb+0x125/0x420 fs/fs-writeback.c:1949 wb_writeback+0x440/0x7b0 fs/fs-writeback.c:2054 wb_check_start_all fs/fs- writeback.c:2176 [インライン] wb_do_writeback fs/fs-writeback.c:2202 [インライン] wb_workfn+0x827/0xef0 fs/fs-writeback.c:2235 process_one_work+0x877/0xdb0 kernel/workqueue.c:2289 worker_thread+0xb14 /0x1330 kernel/workqueue.c:2436 kthread+0x266/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> BUG_ON() はここで発生します/*ノードが使用するリソースの破棄 */ void hfs_bnode_put(struct hfs_bnode *node) {if (node) { <skipped> BUG_ON(!atomic_read(&node->refcnt)); <- ここに問題があります!!! <skipped> } } refcntをトレースすることで、ノードがrefcnt 1を持つhfs_bmap_alloc()によって作成されることがわかりました。その後、ノードはhfs_btree_write()によって使用されます。ノードを見つけた後に、hfs_bnode_get() がありません。問題は次のパスで発生しました <alloc> hfs_bmap_alloc hfs_bnode_find __hfs_bnode_create <- refcnt 1で新しいノードを割り当てます hfs_bnode_put <- refcntを減らします <write> hfs_btree_write hfs_bnode_find __hfs_bnode_create hfs_bnode_findhash <- refcntが増加せずにノードを見つけます。 hfs_bnode_put <- refcnt が 0 であるために、BUG_ON() をトリガーしますCVE-2023-53862]

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

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

  - hfs: fix missing hfs_bnode_get() in __hfs_bnode_create Syzbot found a kernel BUG in hfs_bnode_put():
    kernel BUG at fs/hfs/bnode.c:466! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 3634 Comm:
    kworker/u4:5 Not tainted 6.1.0-rc7-syzkaller-00190-g97ee9d1c1696 #0 Hardware name: Google Google Compute     Engine/Google Compute Engine, BIOS Google 10/26/2022 Workqueue: writeback wb_workfn (flush-7:0) RIP:
    0010:hfs_bnode_put+0x46f/0x480 fs/hfs/bnode.c:466 Code: 8a 80 ff e9 73 fe ff ff 89 d9 80 e1 07 80 c1 03 38     c1 0f 8c a0 fe ff ff 48 89 df e8 db 8a 80 ff e9 93 fe ff ff e8 a1 68 2c ff <0f> 0b e8 9a 68 2c ff 0f 0b 0f     1f 84 00 00 00 00 00 55 41 57 41 56 RSP: 0018:ffffc90003b4f258 EFLAGS: 00010293 RAX: ffffffff825e318f RBX:
    0000000000000000 RCX: ffff8880739dd7c0 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000     RBP: ffffc90003b4f430 R08: ffffffff825e2d9b R09: ffffed10045157d1 R10: ffffed10045157d1 R11:
    1ffff110045157d0 R12: ffff8880228abe80 R13: ffff88807016c000 R14: dffffc0000000000 R15: ffff8880228abe00     FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000     CR0: 0000000080050033 CR2: 00007fa6ebe88718 CR3: 000000001e93d000 CR4: 00000000003506f0 DR0:
    0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0     DR7: 0000000000000400 Call Trace: <TASK> hfs_write_inode+0x1bc/0xb40 write_inode fs/fs-writeback.c:1440     [inline] __writeback_single_inode+0x4d6/0x670 fs/fs-writeback.c:1652 writeback_sb_inodes+0xb3b/0x18f0     fs/fs-writeback.c:1878 __writeback_inodes_wb+0x125/0x420 fs/fs-writeback.c:1949 wb_writeback+0x440/0x7b0     fs/fs-writeback.c:2054 wb_check_start_all fs/fs-writeback.c:2176 [inline] wb_do_writeback fs/fs-     writeback.c:2202 [inline] wb_workfn+0x827/0xef0 fs/fs-writeback.c:2235 process_one_work+0x877/0xdb0     kernel/workqueue.c:2289 worker_thread+0xb14/0x1330 kernel/workqueue.c:2436 kthread+0x266/0x300     kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> The BUG_ON() is     triggered at here: /* Dispose of resources used by a node */ void hfs_bnode_put(struct hfs_bnode *node) {     if (node) { <skipped> BUG_ON(!atomic_read(&node->refcnt)); <- we have issue here!!!! <skipped> } } By     tracing the refcnt, I found the node is created by hfs_bmap_alloc() with refcnt 1. Then the node is used     by hfs_btree_write(). There is a missing of hfs_bnode_get() after find the node. The issue happened in     following path: <alloc> hfs_bmap_alloc hfs_bnode_find __hfs_bnode_create <- allocate a new node with     refcnt 1. hfs_bnode_put <- decrease the refcnt <write> hfs_btree_write hfs_bnode_find __hfs_bnode_create     hfs_bnode_findhash <- find the node without refcnt increased. hfs_bnode_put <- trigger the BUG_ON() since     refcnt is 0. (CVE-2023-53862)

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

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

  - hfs修复 __hfs_bnode_create 中缺少的 hfs_bnode_get() Syzbot 在 hfs_bnode_put() 中发现一个内核缺陷
    fs/hfs/bnode.c:466! 的内核缺陷无效的 opcode0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 3634 Comm
    kworker/u4:5 未受感染 6.1.0-rc7-syzkaller-00190-g97ee9d1c1696 #0 硬件名称Google Google Compute Engine/Google Compute Engine、BIOS Google 10/26/2022 Workqueuewriteback wb_workfn (flush-7:0) RIP
    0010hfs_bnode_put+0x46f/0x480 fs/hfs/bnode.c:466 代码8a 80 ff e9 73 fe ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c a0 fe ff ff 48 89 df e8 db 8a 80 ff e9 93 fe ff ff e8 a1 68 2c ff <0f> 0b e8 9a 68 2c ff 0f 0b 0f 1f 84 00 00 00 00 00 55 41 57 41 56 RSP0018:ffffc90003b4f258 EFLAGS: 00010293 RAX: ffff8fff84
    0000000000000000 RCX: ffff8880739dd7c0 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc90003b4f430 R08: ffffffff825e2d9b R09: ffffed10045157d1 R10: ffffed10045157d1 R11:
     R121ffff110045157d0  : ffff8880228abe80 R13: ffff88807016c000 R14: dffffc0000000000 R15: ffff8880228abe00 FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fa6ebe88718 CR3: 000000001e93d000 CR4: 00000000003506f0 DR0
    0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> hfs_write_inode+0x1bc/0xb40 write_inode fs/fs-writeback.c:1440 [inline] __writeback_single_inode+0x4d6/0x670 fs/fs-writeback. c:1652 writeback_sb_inodes+0xb3b/0x18f0 fs/fs-writeback.c:1878 __writeback_inodes_wb+0x125/0x420 fs/fs-writeback.c:1949 wb_writeback+0x440/0x7b0 fs/fs-writeback.c:2054 wb_check_start_all fs/fs- writeback.c:2176 [内联] wb_do_writeback fs/fs-writeback.c:2202 [内联] wb_workfn+0x827/0xef0 fs/fs-writeback.c:2235 process_one_work+0x877/0xdb0 kernel/workqueue.c:2289 work_thread+0xb14 /0x1330 kernel/workqueue.c:2436 kthread+0x266/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> BUG_ON() 在以下位置触发/*释放节点使用的资源 */ void hfs_bnode_put(struct hfs_bnode *node) {if (node) { <skipped> BUG_ON(!atomic_read(&node->refcnt)); <- 此处有问题!!!! <skipped> 通过跟踪 refcnt我发现 hfs_bmap_alloc() refcnt 为 1 创建该节点。然后 hfs_btree_write() 使用该节点。找到节点后缺少 hfs_bnode_get()。以下路径中会发生问题 <alloc> hfs_bmap_alloc hfs_bnode_find __hfs_bnode_create <- 以 refcnt 分配新节点 1. hfs_bnode_put <- 减少 refcnt <write> hfs_btree_write hfs_bnode_find __hfs_bnode_create hfs_bnode_findhash <- 增加 refcnt 时查找节点。 hfs_bnode_put <- 触发 BUG_ON() 因为 refcnt 为 0。(CVE-2023-53862]

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

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

  - hfs修正 __hfs_bnode_create 中遺漏的 hfs_bnode_get() Syzbot 在 hfs_bnode_put() 中發現一個核心錯誤
    fs/hfs/bnode.c:466! 的核心錯誤無效 opcode0000 [#1] PREEMPT SMP KASAN CPU0 PID3634 Comm
    kworker/u4:5 未受污染的 6.1.0-rc7-syzkaller-00190-g97ee9d1c1696 #0 硬體名稱Google Google Compute Engine/Google Compute Engine、BIOS Google 2022 年 10 月 26 日 工作佇列 writeback wb_workfn (flush-7:0) RIP
    0010:hfs_bnode_put+0x46f/0x480 fs/hfs/bnode.c:466 程式碼8a 80 ff e9 73 fe ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c a0 fe ff ff 48 89 df e8 db 8a 80 ff e9 93 fe ff ff e8 a1 68 2c ff <0f> 0b e8 9a 68 2c ff 0f 0b 0f 1f 84 00 00 00 00 00 55 41 57 41 56 RSP: 0018:ffffc90003b4f258 EFLAGS: 0000010293 RAX: 18f ffffffff8556
    0000000000000000 RCX: ffff8880739dd7c0 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc90003b4f430 R08: ffffffff825e2d9b R09: ffffed10045157d1 R10: ffffed10045157d1 R11:
     R121ffff110045157d0  : ffff8880228abe80 R13: ffff88807016c000 R14: dffffc0000000000 R15: ffff8880228abe00 FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fa6ebe88718 CR3: 000000001e93d000 CR4: 00000000003506f0 DR0
    0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> hfs_write_inode+0x1bc/0xb40 write_inode fs/fs-writeback.c:1440 [inline] __writeback_single_inode+0x4d6/0x670 fs/fs-writeback. c:1652 writeback_sb_inodes+0xb3b/0x18f0 fs/fs-writeback.c:1878 __writeback_inodes_wb+0x125/0x420 fs/fs-writeback.c:1949 wb_writeback+0x440/0x7b0 fs/fs-writeback.c:2054 wb_check_start_all fs/fs- writeback.c:2176 [內嵌] wb_do_writeback fs/fs-writeback.c:2202 [內嵌] wb_workfn+0x827/0xef0 fs/fs-writeback.c:2235 process_one_work+0x877/0xdb0 kernel/workqueue.c:2289 worker_thread+0xb14 /0x1330 kernel/workqueue.c:2436 kthread+0x266/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> BUG_ON() 會在此觸發/*棄置節點所用的資源 */ void hfs_bnode_put(struct hfs_bnode *node) {if (node) { <skipped> BUG_ON(!atomic_read(&node->refcnt)); <- 我們有問題!!!! <skipped> 透過追踪 refcnt我發現節點是由 hfs_bmap_alloc() 以 refcnt 1 所建立。然後 hfs_btree_write() 會使用該節點。尋找節點後缺少 hfs_bnode_get()。下列路徑發生問題 <alloc> hfs_bmap_alloc hfs_bnode_find __hfs_bnode_create <- 以 refcnt 配置新節點。hfs_bnode_put <- 減少 refcnt <write> hfs_btree_write hfs_bnode_find __hfs_bnode_create hfs_bnode_findhash <- 尋找沒有 refcnt 的節點增加。 hfs_bnode_put <- 觸發 BUG_ON()因為 refcnt 為 0。(CVE-2023-53862)

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

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

Detections

Analytics

Plugins Search

high

high

high

high