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

  - 已修复 Linux 内核中的下列漏洞：smp: Make CSD lock acquisition atomic for debug mode Commit b0473dcd4b1d (smp: Improve smp_call_function_single() CSD-lock diagnostics) changed smp_call_function_single() so that, when CSD lock debugging is enabled, async !wait calls use the destination CPU csd_data. That improves diagnostics, but it also removes the single-writer property that made the old csd_lock() safe: multiple CPUs can now prepare the same destination CPU CSD concurrently.
    csd_lock() currently waits for CSD_FLAG_LOCK to clear and then sets the bit with a non-atomic read-modify-write. Two senders can both see an unlocked CSD, set the bit, overwrite the callback fields, and enqueue the same llist node. Re-adding a node that is already the queue head can make node->next point to itself, leaving the target CPU stuck walking call_single_queue. Later synchronous work, such as a TLB shootdown, can then remain queued and trigger soft-lockup warnings or panics. Keep the single csd_lock() implementation, but when CSD lock debugging is enabled, acquire CSD_FLAG_LOCK with try_cmpxchg_acquire().
    This makes the destination CPU CSD a real atomic lock in the only configuration where it can be shared by multiple remote senders, while preserving the existing non-debug fast path. (CVE-2026-68438)

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

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

  - 已解決 Linux 核心中的下列弱點：smp: Make CSD lock acquisition atomic for debug mode Commit b0473dcd4b1d (smp: Improve smp_call_function_single() CSD-lock diagnostics) changed smp_call_function_single() so that, when CSD lock debugging is enabled, async !wait calls use the destination CPU csd_data. That improves diagnostics, but it also removes the single-writer property that made the old csd_lock() safe: multiple CPUs can now prepare the same destination CPU CSD concurrently.
    csd_lock() currently waits for CSD_FLAG_LOCK to clear and then sets the bit with a non-atomic read-modify-write. Two senders can both see an unlocked CSD, set the bit, overwrite the callback fields, and enqueue the same llist node. Re-adding a node that is already the queue head can make node->next point to itself, leaving the target CPU stuck walking call_single_queue. Later synchronous work, such as a TLB shootdown, can then remain queued and trigger soft-lockup warnings or panics. Keep the single csd_lock() implementation, but when CSD lock debugging is enabled, acquire CSD_FLAG_LOCK with try_cmpxchg_acquire().
    This makes the destination CPU CSD a real atomic lock in the only configuration where it can be shared by multiple remote senders, while preserving the existing non-debug fast path. (CVE-2026-68438)

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

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

  - Linux カーネルでは、以下の脆弱性が解決されています: smp: Make CSD lock acquisition atomic for debug mode Commit b0473dcd4b1d (smp: Improve smp_call_function_single() CSD-lock diagnostics) changed smp_call_function_single() so that, when CSD lock debugging is enabled, async !wait calls use the destination CPU csd_data. That improves diagnostics, but it also removes the single-writer property that made the old csd_lock() safe: multiple CPUs can now prepare the same destination CPU CSD concurrently.
    csd_lock() currently waits for CSD_FLAG_LOCK to clear and then sets the bit with a non-atomic read-modify-write. Two senders can both see an unlocked CSD, set the bit, overwrite the callback fields, and enqueue the same llist node. Re-adding a node that is already the queue head can make node->next point to itself, leaving the target CPU stuck walking call_single_queue. Later synchronous work, such as a TLB shootdown, can then remain queued and trigger soft-lockup warnings or panics. Keep the single csd_lock() implementation, but when CSD lock debugging is enabled, acquire CSD_FLAG_LOCK with try_cmpxchg_acquire().
    This makes the destination CPU CSD a real atomic lock in the only configuration where it can be shared by multiple remote senders, while preserving the existing non-debug fast path. (CVE-2026-68438)

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

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

  - In the Linux kernel, the following vulnerability has been resolved: smp: Make CSD lock acquisition atomic     for debug mode Commit b0473dcd4b1d (smp: Improve smp_call_function_single() CSD-lock diagnostics)     changed smp_call_function_single() so that, when CSD lock debugging is enabled, async !wait calls use the     destination CPU csd_data. That improves diagnostics, but it also removes the single-writer property that     made the old csd_lock() safe: multiple CPUs can now prepare the same destination CPU CSD concurrently.
    csd_lock() currently waits for CSD_FLAG_LOCK to clear and then sets the bit with a non-atomic read-modify-     write. Two senders can both see an unlocked CSD, set the bit, overwrite the callback fields, and enqueue     the same llist node. Re-adding a node that is already the queue head can make node->next point to itself,     leaving the target CPU stuck walking call_single_queue. Later synchronous work, such as a TLB shootdown,     can then remain queued and trigger soft-lockup warnings or panics. Keep the single csd_lock()     implementation, but when CSD lock debugging is enabled, acquire CSD_FLAG_LOCK with try_cmpxchg_acquire().
    This makes the destination CPU CSD a real atomic lock in the only configuration where it can be shared by     multiple remote senders, while preserving the existing non-debug fast path. (CVE-2026-68438)

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
335289	Linux Distros 未修补的漏洞：CVE-2026-68438	Nessus	Misc.	2026/8/13	2026/8/19	high
335289	Linux Distros 未修補弱點：CVE-2026-68438	Nessus	Misc.	2026/8/13	2026/8/19	high
335289	Linux Distros のパッチ未適用の脆弱性: CVE-2026-68438	Nessus	Misc.	2026/8/13	2026/8/19	high
335289	Linux Distros Unpatched Vulnerability : CVE-2026-68438	Nessus	Misc.	2026/8/13	2026/8/19	high

偵測

搜尋 Plugin

high

high

high

high