<?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:49:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50010 — exec: don't WARN for racy path_noexec check</title>
      <link>https://db.gcve.eu/vuln/cve-2024-50010</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exec: don&amp;#39;t WARN for racy path_noexec check&lt;/p&gt;
&lt;p&gt;Both i_mode and noexec checks wrapped in WARN_ON stem from an artifact
of the previous implementation. They used to legitimately check for the
condition, but that got moved up in two commits:
633fb6ac3980 (&amp;#34;exec: move S_ISREG() check earlier&amp;#34;)
0fd338b2d2cd (&amp;#34;exec: move path_noexec() check earlier&amp;#34;)&lt;/p&gt;
&lt;p&gt;Instead of being removed said checks are WARN_ON&amp;#39;ed instead, which
has some debug value.&lt;/p&gt;
&lt;p&gt;However, the spurious path_noexec check is racy, resulting in
unwarranted warnings should someone race with setting the noexec flag.&lt;/p&gt;
&lt;p&gt;One can note there is more to perm-checking whether execve is allowed
and none of the conditions are guaranteed to still hold after they were
tested for.&lt;/p&gt;
&lt;p&gt;Additionally this does not validate whether the code path did any perm
checking to begin with -- it will pass if the inode happens to be
regular.&lt;/p&gt;
&lt;p&gt;Keep the redundant path_noexec() check even though it&amp;#39;s mindless
nonsense checking for guarantee that isn&amp;#39;t given so drop the WARN.&lt;/p&gt;
&lt;p&gt;Reword the commentary and do small tidy ups while here.&lt;/p&gt;
&lt;p&gt;[brauner: keep redundant path_noexec() check]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exec: don&amp;#39;t WARN for racy path_noexec check&lt;/p&gt;
&lt;p&gt;Both i_mode and noexec checks wrapped in WARN_ON stem from an artifact
of the previous implementation. They used to legitimately check for the
condition, but that got moved up in two commits:
633fb6ac3980 (&amp;#34;exec: move S_ISREG() check earlier&amp;#34;)
0fd338b2d2cd (&amp;#34;exec: move path_noexec() check earlier&amp;#34;)&lt;/p&gt;
&lt;p&gt;Instead of being removed said checks are WARN_ON&amp;#39;ed instead, which
has some debug value.&lt;/p&gt;
&lt;p&gt;However, the spurious path_noexec check is racy, resulting in
unwarranted warnings should someone race with setting the noexec flag.&lt;/p&gt;
&lt;p&gt;One can note there is more to perm-checking whether execve is allowed
and none of the conditions are guaranteed to still hold after they were
tested for.&lt;/p&gt;
&lt;p&gt;Additionally this does not validate whether the code path did any perm
checking to begin with -- it will pass if the inode happens to be
regular.&lt;/p&gt;
&lt;p&gt;Keep the redundant path_noexec() check even though it&amp;#39;s mindless
nonsense checking for guarantee that isn&amp;#39;t given so drop the WARN.&lt;/p&gt;
&lt;p&gt;Reword the commentary and do small tidy ups while here.&lt;/p&gt;
&lt;p&gt;[brauner: keep redundant path_noexec() check]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-50010</guid>
    </item>
    <item>
      <title>USN-7276-1 — linux, linux-lowlatency vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7276-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.10: linux, Ubuntu:24.10: linux-lowlatency&lt;/p&gt;
&lt;p&gt;Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)&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:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - SuperH RISC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - RAM backed block device driver;
  - Network block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - TPM device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - Buffer Sharing and Synchronization framework;
  - EDAC drivers;
  - FireWire subsystem;
  - ARM SCMI message protocol;
  - ARM SCPI message protocol;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.10: linux, Ubuntu:24.10: linux-lowlatency&lt;/p&gt;
&lt;p&gt;Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)&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:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - SuperH RISC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - RAM backed block device driver;
  - Network block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - TPM device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - Buffer Sharing and Synchronization framework;
  - EDAC drivers;
  - FireWire subsystem;
  - ARM SCMI message protocol;
  - ARM SCPI message protocol;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7276-1</guid>
    </item>
  </channel>
</rss>
