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

  - pidpid_nr_ns __task_pid_nr_ns ns = task_active_pid_ns(current) で ns null に対する判定を追加します
    pid_nr_ns(rcu_dereference(*task_pid_ptr(task, type)), ns); if (pid && ns->level <= pid->level) { task_active_pid_ns に null が返されることがあります。その後、pid_nr_ns でカーネルパニックをトリガーします。例:
    仮想アドレスでカーネルの NULL ポインターデリファレンスを処理できません 000000000000058 Mem abort infoESR = 0x0000000096000007 EC = 0x25DABT最新の EL、IL = 32 ビット SET = 0、FnV = EA = 0、S1PTW = 0 FSC = 0x07レベル 3 変換障害データ中止情報ISV = 0、ISS = 0x00000007、ISS2 = 0x00000000 CM = 0、WnR = 0、TnD = 0、TagAccess = 0 GCS = 0、Overlay = 0、DirtyBit = 0、Xs = 0 user pgtable4k ページ、39 ビット VA、 pgdp=00000002175aa000 [0000000000000058] pgd=08000002175ab003、p4d=08000002175ab003、 pud=08000002175ab003、 pmd=08000002175be003、 pte=0000000000000000 pstate834000c5Nzcv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--pc __task_pid_nr_ns+ 0x74/0xd0 lr __task_pid_nr_ns+0x24/0xd0 sp : ffffffc08001bd10 x29
    ffffffc08001bd10 x28: ffffffd4422b2000 x27: 0000000000000001 x26: ffffffd442821168 x25: ffffffd442821000 x24: 00000f89492eab31 x23: 00000000000000c0 x22: ffffff806f5693c0 x21: ffffff806f5693c0 x20:
    0000000000000001 x19: 0000000000000000 x18: 0000000000000000 x17: 00000000529c6ef0 x16: 00000000529c6ef0 x15: 00000000023a1adc x14: 0000000000000003 x13: 00000000007ef6d8 x12: 001167c391c78800 x11:
    00ffffffffffffff x10: 0000000000000000 x9 : 0000000000000001 x8 : ffffff80816fa3c0 x7 : 0000000000000000 x6 : 49534d702d535449 x5 : ffffffc080c4c2c0 x4 : ffffffd43ee128c8 x3 : ffffffd43ee124dc x2 :
    0000000000000000 x1 : 0000000000000001 x0 : ffffff806f5693c0 Call trace: __task_pid_nr_ns+0x74/0xd0 ...
    __handle_irq_event_percpu+0xd4/0x284 handle_irq_event+0x48/0xb0 handle_fasteoi_irq+0x160/0x2d8 generic_handle_domain_irq+0x44/0x60 gic_handle_irq+0x4c/0x114 call_on_irq_stack+0x3c/0x74 do_interrupt_handler+0x4c/0x84 el1_interrupt+0x34/0x58 el1h_64_irq_handler+0x18/0x24 el1h_64_irq+0x68/0x6c account_kernel_stack+0x60/0x144 exit_task_stack_account+0x1c/0x80 do_exit+0x7e4/0xaf8 ...
    get_signal+0x7bc/0x8d8 do_notify_resume+0x128/0x828 el0_svc+0x6c/0x70 el0t_64_sync_handler+0x68/0xbc el0t_64_sync+0x1a8/0x1ac Code: 35fffe54 911a02a8 f9400108 b4000128 (b9405a69) ---[ end trace 0000000000000000 ]--- Kernel panic - not syncing Oops割り込みでの致命的な例外CVE-2025-40178

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

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

  - pid: Add a judgment for ns null in pid_nr_ns __task_pid_nr_ns ns = task_active_pid_ns(current);
    pid_nr_ns(rcu_dereference(*task_pid_ptr(task, type)), ns); if (pid && ns->level <= pid->level) { Sometimes     null is returned for task_active_pid_ns. Then it will trigger kernel panic in pid_nr_ns. For example:
    Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 Mem abort info: ESR =     0x0000000096000007 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC =     0x07: level 3 translation fault Data abort info: ISV = 0, ISS = 0x00000007, ISS2 = 0x00000000 CM = 0, WnR     = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 39-bit VAs,     pgdp=00000002175aa000 [0000000000000058] pgd=08000002175ab003, p4d=08000002175ab003, pud=08000002175ab003,     pmd=08000002175be003, pte=0000000000000000 pstate: 834000c5 (Nzcv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--)     pc : __task_pid_nr_ns+0x74/0xd0 lr : __task_pid_nr_ns+0x24/0xd0 sp : ffffffc08001bd10 x29:
    ffffffc08001bd10 x28: ffffffd4422b2000 x27: 0000000000000001 x26: ffffffd442821168 x25: ffffffd442821000     x24: 00000f89492eab31 x23: 00000000000000c0 x22: ffffff806f5693c0 x21: ffffff806f5693c0 x20:
    0000000000000001 x19: 0000000000000000 x18: 0000000000000000 x17: 00000000529c6ef0 x16: 00000000529c6ef0     x15: 00000000023a1adc x14: 0000000000000003 x13: 00000000007ef6d8 x12: 001167c391c78800 x11:
    00ffffffffffffff x10: 0000000000000000 x9 : 0000000000000001 x8 : ffffff80816fa3c0 x7 : 0000000000000000     x6 : 49534d702d535449 x5 : ffffffc080c4c2c0 x4 : ffffffd43ee128c8 x3 : ffffffd43ee124dc x2 :
    0000000000000000 x1 : 0000000000000001 x0 : ffffff806f5693c0 Call trace: __task_pid_nr_ns+0x74/0xd0 ...
    __handle_irq_event_percpu+0xd4/0x284 handle_irq_event+0x48/0xb0 handle_fasteoi_irq+0x160/0x2d8     generic_handle_domain_irq+0x44/0x60 gic_handle_irq+0x4c/0x114 call_on_irq_stack+0x3c/0x74     do_interrupt_handler+0x4c/0x84 el1_interrupt+0x34/0x58 el1h_64_irq_handler+0x18/0x24 el1h_64_irq+0x68/0x6c     account_kernel_stack+0x60/0x144 exit_task_stack_account+0x1c/0x80 do_exit+0x7e4/0xaf8 ...
    get_signal+0x7bc/0x8d8 do_notify_resume+0x128/0x828 el0_svc+0x6c/0x70 el0t_64_sync_handler+0x68/0xbc     el0t_64_sync+0x1a8/0x1ac Code: 35fffe54 911a02a8 f9400108 b4000128 (b9405a69) ---[ end trace     0000000000000000 ]--- Kernel panic - not syncing: Oops: Fatal exception in interrupt (CVE-2025-40178)

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

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

  - pid在 pid_nr_ns __task_pid_nr_ns 中添加对 ns null 的判断 ns = task_active_pid_ns(current);
    pid_nr_ns(rcu_dereference(*task_pid_ptr(task, type)), ns); if (pid && ns->level <= pid->level) { 有时会为 task_active_pid_ns 返回 null。然后它将在 pid_nr_ns 中触发内核错误。例如：
    无法处理虚拟地址 0000000000000058 Mem abort infoESR = 0x0000000096000007 EC = 0x25DABT当前 ELIL = 32 位 SET = 0FnV = 0 EA = 0S1PTW = 0 FSC = 0x07级别 3 转换错误数据中止信息ISV = 0、ISS = 0x00000007、ISS2 = 0x00000000 CM = 0、WnR = 0、TnD = 0、TagAccess = 0 GCS = 0、Overlay = 0、DirtyBit = 0、Xs = 0 用户pgtable4k 页面、39 位 VA、 pgdp=00000002175aa000 [0000000000000058] pgd=08000002175ab003、p4d=08000002175ab003、 pud=08000002175ab003、 pmd=08000002175be003、 pte=0000000000000000 pstate: 834000c5 (Nzcv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--) pc__task_pid_nr_ns+ 0x74/0xd0 lr__task_pid_nr_ns+0x24/0xd0 spffffffc08001bd10 x29
    ffffffc08001bd10 x28: ffffffd4422b2000 x27: 0000000000000001 x26: ffffffd442821168 x25: ffffffd442821000 x24: 00000f89492eab31 x23: 00000000000000c0 x22: ffffff806f5693c0 x21: ffffff806f5693c0 x20:
    0000000000000001 x19: 0000000000000000 x18: 0000000000000000 x17: 00000000529c6ef0 x16: 00000000529c6ef0 x15: 00000000023a1adc x14: 0000000000000003 x13: 00000000007ef6d8 x12: 001167c391c78800 x11:
    00ffffffffffffff x10: 0000000000000000 x9 : 0000000000000001 x8 : ffffff80816fa3c0 x7 : 0000000000000000 x6 : 49534d702d535449 x5 : ffffffc080c4c2c0 x4 : ffffffd43ee128c8 x3 : ffffffd43ee124dc x2 :
    0000000000000000 x1 : 0000000000000001 x0 : ffffff806f5693c0 调用跟踪 __task_pid_nr_ns+0x74/0xd0 ...
    __handle_irq_event_percpu+0xd4/0x284 handle_irq_event+0x48/0xb0 handle_fasteoi_irq+0x160/0x2d8 generic_handle_domain_irq+0x44/0x60 gic_handle_irq+0x4c/0x114 call_on_irq_stack+0x3c/0x74 do_interrupt_handler+0x4c/0x84 el1_interrupt+0x34/0x58 el1h_64_irq_handler+0x18/0x24 el1h_64_irq+0x68/0x6c account_kernel_stack+0x60/0x144 exit_task_stack_account+0x1c/0x80 do_exit+0x7e4/0xaf8 ...
    get_signal+0x7bc/0x8d8 do_notify_resume+0x128/0x828 el0_svc+0x6c/0x70 el0t_64_sync_handler+0x68/0xbc el0t_64_sync+0x1a8/0x1ac Code: 35fffe54 911a02a8 f9400108 b4000128 (b9405a69) ---[ end trace 0000000000000000 ]--- Kernel panic - not syncing Oops中断中的致命异常 (CVE-2025-40178)

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

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

  - pid針對 pid_nr_ns __task_pid_nr_ns ns = task_active_pid_ns(current); 中的 ns null 新增判斷
    pid_nr_ns(rcu_dereference(*task_pid_ptr(task, type)), ns) if (pid && ns->level <= pid->level) { 有時會針對 task_active_pid_ns 傳回 null。然後會在 pid_nr_ns 中觸發核心錯誤。例如：
    無法處理虛擬位址 0000000000000058 的核心 NULL 指標解除參照。層級 3 轉譯錯誤資料中止資訊ISV = 0、ISS = 0x00000000 CM = 0、WnR = 0、TnD = 0、TagAccess = 0 GCS = 0、Overlay = 0、DirtyBit = 0、Xs = 0 使用者pgtable4k 頁面39 位元 VA、 pgdp=00000002175aa000 [0000000000000058] pgd=08000002175ab003、p4d=08000002175ab003、 pud=08000002175ab003、 pmd=08000002175be003、 pte=0000000000000000 pstate: 834000c5 (Nzcv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--) pc __task_pid_nr_ns+ 0x74/0xd0 lr __task_pid_nr_ns+0x24/0xd0 sp ffffffc08001bd10 x29
    ffffffc08001bd10 x28: ffffffd4422b2000 x27: 0000000000000001 x26: ffffffd442821168 x25: ffffffd442821000 x24: 00000f89492eab31 x23: 00000000000000c0 x22: ffffff806f5693c0 x21: ffffff806f5693c0 x20:
    0000000000000001 x19: 0000000000000000 x18: 0000000000000000 x17: 00000000529c6ef0 x16: 00000000529c6ef0 x15: 00000000023a1adc x14: 0000000000000003 x13: 00000000007ef6d8 x12: 001167c391c78800 x11:
    00ffffffffffffff x10: 0000000000000000 x9 : 0000000000000001 x8 : ffffff80816fa3c0 x7 : 0000000000000000 x6 : 49534d702d535449 x5 : ffffffc080c4c2c0 x4 : ffffffd43ee128c8 x3 : ffffffd43ee124dc x2 :
    0000000000000000 x1 0000000000000001 x0 ffffff806f5693c0 呼叫追踪 __task_pid_nr_ns+0x74/0xd0 ...
    __handle_irq_event_percpu+0xd4/0x284 handle_irq_event+0x48/0xb0 handle_fasteoi_irq+0x160/0x2d8 generic_handle_domain_irq+0x44/0x60 gic_handle_irq+0x4c/0x114 call_on_irq_stack+0x3c/0x74 do_interrupt_handler+0x4c/0x84 el1_interrupt+0x34/0x58 el1h_64_irq_handler+0x18/0x24 el1h_64_irq+0x68/0x6c account_kernel_stack+0x60/0x144 exit_task_stack_account+0x1c/0x80 do_exit+0x7e4/0xaf8 ...
    get_signal+0x7bc/0x8d8 do_notify_resume+0x128/0x828 el0_svc+0x6c/0x70 el0t_64_sync_handler+0x68/0xbc el0t_64_sync+0x1a8/0x1ac Code: 35fffe54 911a02a8 f9400108 b4000128 (b9405a69) ---[ end trace 0000000000000000 ]--- Kernel panic - not syncing Oops中斷中的嚴重例外狀況 (CVE-2025-40178)

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

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

Detections

Analytics

Plugins Search

medium

medium

medium

medium