https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 02:12:01 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-13717 bdu:2025-13717 https://cve.radiocsirt.org/vuln/bdu:2025-13717 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057 certfr-2025-avi-1057 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057 https://cve.radiocsirt.org/vuln/euvd-2026-344430 EUVD-2026-344430 https://cve.radiocsirt.org/vuln/euvd-2026-344430 https://cve.radiocsirt.org/vuln/fkie_cve-2021-47226 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer</p> <p>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.</p> <p>__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.</p> <p>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&#39;s user-visible state.</p> <p>Invalidate preserved FPU registers on XRSTOR failure to prevent this situation from corrupting any state.</p> <p>[1] Frequent readers of the errata lists might imagine &#34;complex microarchitectural conditions&#34;.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer</p> <p>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.</p> <p>__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.</p> <p>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&#39;s user-visible state.</p> <p>Invalidate preserved FPU registers on XRSTOR failure to prevent this situation from corrupting any state.</p> <p>[1] Frequent readers of the errata lists might imagine &#34;complex microarchitectural conditions&#34;.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-47226 https://cve.radiocsirt.org/vuln/ghsa-4jxh-jrgp-4422 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer</p> <p>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.</p> <p>__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.</p> <p>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&#39;s user-visible state.</p> <p>Invalidate preserved FPU registers on XRSTOR failure to prevent this situation from corrupting any state.</p> <p>[1] Frequent readers of the errata lists might imagine &#34;complex microarchitectural conditions&#34;.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer</p> <p>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.</p> <p>__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.</p> <p>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&#39;s user-visible state.</p> <p>Invalidate preserved FPU registers on XRSTOR failure to prevent this situation from corrupting any state.</p> <p>[1] Frequent readers of the errata lists might imagine &#34;complex microarchitectural conditions&#34;.</p> https://cve.radiocsirt.org/vuln/ghsa-4jxh-jrgp-4422 https://cve.radiocsirt.org/vuln/gsd-2021-47226 gsd-2021-47226 https://cve.radiocsirt.org/vuln/gsd-2021-47226 https://cve.radiocsirt.org/vuln/rhsa-2021:4356 <p>kernel: Intel graphics card information leak. kernel: Overlayfs in the Linux kernel and shiftfs not restoring original value on error leading to a refcount underflow kernel: out-of-bounds reads in pinctrl subsystem. kernel: Improper input validation in some Intel(R) Ethernet E810 Adapter drivers kernel: Insufficient access control in some Intel(R) Ethernet E810 Adapter drivers kernel: Uncontrolled resource consumption in some Intel(R) Ethernet E810 Adapter drivers kernel: Fragmentation cache not cleared on reconnection kernel: Reassembling fragments encrypted under different keys kernel: wifi frame payload being parsed incorrectly as an L2 frame kernel: Forwarding EAPOL from unauthenticated wifi client kernel: accepting plaintext data frames in protected networks kernel: not verifying TKIP MIC of fragmented frames kernel: accepting fragmented plaintext frames in protected networks kernel: accepting unencrypted A-MSDU frames that start with RFC1042 header kernel: accepting plaintext broadcast fragments as full frames kernel: reassembling encrypted fragments with non-consecutive packet numbers kernel: reassembling mixed encrypted/plaintext fragments kernel: powerpc: RTAS calls can be used to compromise kernel integrity kernel: the copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check kernel: locking inconsistency in drivers/tty/tty_io.c and drivers/tty/tty_jobctrl.c can lead to a read-after-free kernel: buffer overf…</p> <p>kernel: Intel graphics card information leak. kernel: Overlayfs in the Linux kernel and shiftfs not restoring original value on error leading to a refcount underflow kernel: out-of-bounds reads in pinctrl subsystem. kernel: Improper input validation in some Intel(R) Ethernet E810 Adapter drivers kernel: Insufficient access control in some Intel(R) Ethernet E810 Adapter drivers kernel: Uncontrolled resource consumption in some Intel(R) Ethernet E810 Adapter drivers kernel: Fragmentation cache not cleared on reconnection kernel: Reassembling fragments encrypted under different keys kernel: wifi frame payload being parsed incorrectly as an L2 frame kernel: Forwarding EAPOL from unauthenticated wifi client kernel: accepting plaintext data frames in protected networks kernel: not verifying TKIP MIC of fragmented frames kernel: accepting fragmented plaintext frames in protected networks kernel: accepting unencrypted A-MSDU frames that start with RFC1042 header kernel: accepting plaintext broadcast fragments as full frames kernel: reassembling encrypted fragments with non-consecutive packet numbers kernel: reassembling mixed encrypted/plaintext fragments kernel: powerpc: RTAS calls can be used to compromise kernel integrity kernel: the copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check kernel: locking inconsistency in drivers/tty/tty_io.c and drivers/tty/tty_jobctrl.c can lead to a read-after-free kernel: buffer overf…</p> https://cve.radiocsirt.org/vuln/rhsa-2021:4356 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47226 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 84 more</p> <p>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&#39;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 &#34;complex microarchitectural conditions&#34;.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 84 more</p> <p>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&#39;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 &#34;complex microarchitectural conditions&#34;.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47226