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

  - x86/fpu在使用者緩衝區的 XRSTOR 失敗後使 FPU 狀態失效。Intel 和 AMD 都認為 XRSTOR 在架構上失敗並出現 #PF 錯誤但仍變更暫存器狀態在架構上是有效的。可能發生此問題的實際情況不清楚 [1]但如果同級執行緒取消對應頁面並使共用 TLB 無效而另一個同級執行緒在有問題的頁面上執行 XRSTOR似乎有可能觸發此情形。 __fpu__restore_sig() 在代表不同受害工作保留硬體暫存器時 (使用 fpu_fpregs_owner_ctx 機制) 可執行 XRSTOR且理論上 XRSTOR 可能會失敗但會修改暫存器。如果發生此情況則有一個視窗在此期間__fpu__restore_sig() 可向外排程受害工作可在不重新載入其 FPU 暫存器的情況下重新排程。這會導致將 __fpu__restore_sig() 嘗試載入的 FPU 狀態的一部分洩漏到受害者工作的使用者可見狀態中。XRSTOR 失敗時使保留的 FPU 暫存器失效以防止此情況損毀任何狀態。 [1] 錯字勘誤表清單的常讀者可能會想像到復雜的微架構情況。 (CVE-2021-47226)

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

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

  - x86/fpu在用户缓冲区的 XRSTOR 失败后使 FPU 状态无效 Intel 和 AMD 都认为 XRSTOR 在架构上有效以 #PF 失败但仍然更改了寄存器状态。尚不清楚在什么情况下可能发生此问题 [1] 但似乎有可能是因为当一个同级线程取消映射某个页面并使共享的 TLB 无效同时另一个同级线程正在相关页面上执行 XRSTOR 时可能会触发此问题。当为其他受害者任务保留硬件寄存器时__fpu__restore_sig() 可执行 XRSTOR使用 fpu_fpregs_owner_ctx 机制理论上XRSTOR 可能会失败但会修改寄存器。如果发生这种情况则存在一个窗口__fpu__restore_sig() 可以在该窗口中安排退出而受害者任务可以在不重新加载其自己的 FPU 寄存器的情况下安排回该窗口。这可导致 __fpu__restore_sig() 尝试加载的部分 FPU 状态泄漏到受害者任务的用户可见状态中。使 XRSTOR 出现故障时保留的 FPU 寄存器无效以防止这种情况损坏任何状态。 [1] 勘误表列表的经常阅读者可能会想像到复杂的微架构情况。 (CVE-2021-47226)

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

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

  - x86/fpuユーザーバッファからの失敗した XRSTOR の後に FPU 状態を無効化。Intel と AMD のどちらも、#PF で失敗する XRSTOR がアーキテクチャ上有効であると考えますが、依然としてレジスタの状態を変更します。これが発生する実際の条件は不明 [1] ですが、問題のページ上で他の兄弟スレッドが XRSTOR を実行している間に、1 つの兄弟スレッドがページをアンマッピングし、共有された TLB を無効化した場合、これが発生する可能性があるようです。 __fpu__restore_sig() は、fpu_fpregs_owner_ctx メカニズムを使用して別の被害者タスクの代わりにハードウェアレジスタが保存されている間に、XRSTOR を実行でき、理論上は、XRSTOR は失敗しますがレジスタを変更する可能性があります。これが発生すると、__fpu__restore_sig() がスケジュールアウトし、被害者のタスクが自身の FPU レジスターをリロードせずにバックスケジュールを設定することができるウィンドウが存在します。これにより、__fpu__restore_sig()が被害者タスクのユーザーの可視的な状態に漏えいをロードしようとしたFPU状態の一部が生じます。この状況が状態を破損させないように、XRSTOR エラーで保存された FPU レジスタを無効化します。 [1] エラータリストを頻繁に閲覧するユーザーは、複雑なマイクロアーキテクチャー状態をイメージできるかもしれません。CVE-2021-47226

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

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

  - x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer Both Intel and AMD consider it to     be architecturally valid for XRSTOR to fail with #PF but nonetheless change the register state. The actual     conditions under which this might occur are unclear [1], but it seems plausible that this might be     triggered if one sibling thread unmaps a page and invalidates the shared TLB while another sibling thread     is executing XRSTOR on the page in question. __fpu__restore_sig() can execute XRSTOR while the hardware     registers are preserved on behalf of a different victim task (using the fpu_fpregs_owner_ctx mechanism),     and, in theory, XRSTOR could fail but modify the registers. If this happens, then there is a window in     which __fpu__restore_sig() could schedule out and the victim task could schedule back in without reloading     its own FPU registers. This would result in part of the FPU state that __fpu__restore_sig() was attempting     to load leaking into the victim task's user-visible state. Invalidate preserved FPU registers on XRSTOR     failure to prevent this situation from corrupting any state. [1] Frequent readers of the errata lists     might imagine complex microarchitectural conditions. (CVE-2021-47226)

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-987393 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer

    Both Intel and AMD consider it to be architecturally valid for XRSTOR to     fail with #PF but nonetheless change the register state.  The actual     conditions under which this might occur are unclear [1], but it seems     plausible that this might be triggered if one sibling thread unmaps a page     and invalidates the shared TLB while another sibling thread is executing     XRSTOR on the page in question.

    __fpu__restore_sig() can execute XRSTOR while the hardware registers     are preserved on behalf of a different victim task (using the     fpu_fpregs_owner_ctx mechanism), and, in theory, XRSTOR could fail but     modify the registers.

    If this happens, then there is a window in which __fpu__restore_sig()     could schedule out and the victim task could schedule back in without     reloading its own FPU registers. This would result in part of the FPU     state that __fpu__restore_sig() was attempting to load leaking into the     victim task's user-visible state.

    Invalidate preserved FPU registers on XRSTOR failure to prevent this     situation from corrupting any state.

    [1] Frequent readers of the errata lists might imagine complex         microarchitectural conditions.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-988697 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer

    Both Intel and AMD consider it to be architecturally valid for XRSTOR to     fail with #PF but nonetheless change the register state.  The actual     conditions under which this might occur are unclear [1], but it seems     plausible that this might be triggered if one sibling thread unmaps a page     and invalidates the shared TLB while another sibling thread is executing     XRSTOR on the page in question.

    __fpu__restore_sig() can execute XRSTOR while the hardware registers     are preserved on behalf of a different victim task (using the     fpu_fpregs_owner_ctx mechanism), and, in theory, XRSTOR could fail but     modify the registers.

    If this happens, then there is a window in which __fpu__restore_sig()     could schedule out and the victim task could schedule back in without     reloading its own FPU registers. This would result in part of the FPU     state that __fpu__restore_sig() was attempting to load leaking into the     victim task's user-visible state.

    Invalidate preserved FPU registers on XRSTOR failure to prevent this     situation from corrupting any state.

    [1] Frequent readers of the errata lists might imagine complex         microarchitectural conditions.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
229762	Linux Distros 未修補的弱點：CVE-2021-47226	Nessus	Misc.	2025/3/5	2025/10/28	high
160459	Amazon Linux 2核心 --advisory ALAS2KERNEL-5。10-2022-002 (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
229762	Linux Distros 未修补的漏洞：CVE-2021-47226	Nessus	Misc.	2025/3/5	2025/10/28	high
160459	Amazon Linux 2 内核 --advisory ALAS2KERNEL-5。10-2022-002 (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
229762	Linux Distros のパッチ未適用の脆弱性: CVE-2021-47226	Nessus	Misc.	2025/3/5	2025/10/28	high
160459	Amazon Linux 2kernel、 --advisory ALAS2KERNEL-5。10-2022-002 ALASKERNEL-5.10-2022-002	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
229762	Linux Distros Unpatched Vulnerability : CVE-2021-47226	Nessus	Misc.	2025/3/5	2025/10/28	high
268774	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987393)	Nessus	Unity Linux Local Security Checks	2025/10/7	2025/10/15	high
160459	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2022-002 (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
272898	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988697)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	high
239342	TencentOS Server 4: kernel (TSSA-2024:0981)	Nessus	Tencent Local Security Checks	2025/6/16	2025/12/4	high

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high