<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Nov 2026 17:50:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23114 — arm64/fpsimd: ptrace: Fix SVE writes on !SME systems</title>
      <link>https://db.gcve.eu/vuln/cve-2026-23114</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64/fpsimd: ptrace: Fix SVE writes on !SME systems&lt;/p&gt;
&lt;p&gt;When SVE is supported but SME is not supported, a ptrace write to the
NT_ARM_SVE regset can place the tracee into an invalid state where
(non-streaming) SVE register data is stored in FP_STATE_SVE format but
TIF_SVE is clear. This can result in a later warning from
fpsimd_restore_current_state(), e.g.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 7214 at arch/arm64/kernel/fpsimd.c:383 fpsimd_restore_current_state+0x50c/0x748&lt;/p&gt;
&lt;p&gt;When this happens, fpsimd_restore_current_state() will set TIF_SVE,
placing the task into the correct state. This occurs before any other
check of TIF_SVE can possibly occur, as other checks of TIF_SVE only
happen while the FPSIMD/SVE/SME state is live. Thus, aside from the
warning, there is no functional issue.&lt;/p&gt;
&lt;p&gt;This bug was introduced during rework to error handling in commit:&lt;/p&gt;
&lt;p&gt;9f8bf718f2923 (&amp;#34;arm64/fpsimd: ptrace: Gracefully handle errors&amp;#34;)&lt;/p&gt;
&lt;p&gt;... where the setting of TIF_SVE was moved into a block which is only
executed when system_supports_sme() is true.&lt;/p&gt;
&lt;p&gt;Fix this by removing the system_supports_sme() check. This ensures that
TIF_SVE is set for (SVE-formatted) writes to NT_ARM_SVE, at the cost of
unconditionally manipulating the tracee&amp;#39;s saved svcr value. The
manipulation of svcr is benign and inexpensive, and we already do
similar elsewhere (e.g. during signal handling), so I don&amp;#39;t think it&amp;#39;s
worth guarding this with system_supports_sme() checks.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64/fpsimd: ptrace: Fix SVE writes on !SME systems&lt;/p&gt;
&lt;p&gt;When SVE is supported but SME is not supported, a ptrace write to the
NT_ARM_SVE regset can place the tracee into an invalid state where
(non-streaming) SVE register data is stored in FP_STATE_SVE format but
TIF_SVE is clear. This can result in a later warning from
fpsimd_restore_current_state(), e.g.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 7214 at arch/arm64/kernel/fpsimd.c:383 fpsimd_restore_current_state+0x50c/0x748&lt;/p&gt;
&lt;p&gt;When this happens, fpsimd_restore_current_state() will set TIF_SVE,
placing the task into the correct state. This occurs before any other
check of TIF_SVE can possibly occur, as other checks of TIF_SVE only
happen while the FPSIMD/SVE/SME state is live. Thus, aside from the
warning, there is no functional issue.&lt;/p&gt;
&lt;p&gt;This bug was introduced during rework to error handling in commit:&lt;/p&gt;
&lt;p&gt;9f8bf718f2923 (&amp;#34;arm64/fpsimd: ptrace: Gracefully handle errors&amp;#34;)&lt;/p&gt;
&lt;p&gt;... where the setting of TIF_SVE was moved into a block which is only
executed when system_supports_sme() is true.&lt;/p&gt;
&lt;p&gt;Fix this by removing the system_supports_sme() check. This ensures that
TIF_SVE is set for (SVE-formatted) writes to NT_ARM_SVE, at the cost of
unconditionally manipulating the tracee&amp;#39;s saved svcr value. The
manipulation of svcr is benign and inexpensive, and we already do
similar elsewhere (e.g. during signal handling), so I don&amp;#39;t think it&amp;#39;s
worth guarding this with system_supports_sme() checks.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-23114</guid>
    </item>
    <item>
      <title>USN-8570-1 — linux-gcp-6.17, linux-realtime-6.17 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8570-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.17, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.17&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Foo-over-UDP (FOU);
  - ARM64 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Drivers core;
  - Null block device driver;
  - Bluetooth drivers;
  - Counter interface drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - On-Chip Interconnect management framework;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - Multiple devices driver;
  - UACCE accelerator framework;
  - MMC subsystem;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PHY drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - SLIMbus drivers;
  - SPI subsystem;
  - TTY drivers;
  - USB Host Controller drivers;
  - W1 Dallas&amp;#39;s 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - EFI Variable file system;
  - Ext4 file system;
  - File systems infrastructure;
  - FUSE (File system in Userspace);
  - Network file systems library;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - SMB network file system;
  - Memory Management;
  - Memory management;
  - Scheduler infrastructure;
  - Tracing infrast…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.17, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.17&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Foo-over-UDP (FOU);
  - ARM64 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Drivers core;
  - Null block device driver;
  - Bluetooth drivers;
  - Counter interface drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - On-Chip Interconnect management framework;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - Multiple devices driver;
  - UACCE accelerator framework;
  - MMC subsystem;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PHY drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - SLIMbus drivers;
  - SPI subsystem;
  - TTY drivers;
  - USB Host Controller drivers;
  - W1 Dallas&amp;#39;s 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - EFI Variable file system;
  - Ext4 file system;
  - File systems infrastructure;
  - FUSE (File system in Userspace);
  - Network file systems library;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - SMB network file system;
  - Memory Management;
  - Memory management;
  - Scheduler infrastructure;
  - Tracing infrast…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8570-1</guid>
    </item>
  </channel>
</rss>
