<?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:53:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-53130 — nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint</title>
      <link>https://db.gcve.eu/vuln/cve-2024-53130</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;nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint&lt;/p&gt;
&lt;p&gt;When using the &amp;#34;block:block_dirty_buffer&amp;#34; tracepoint, mark_buffer_dirty()
may cause a NULL pointer dereference, or a general protection fault when
KASAN is enabled.&lt;/p&gt;
&lt;p&gt;This happens because, since the tracepoint was added in
mark_buffer_dirty(), it references the dev_t member bh-&amp;gt;b_bdev-&amp;gt;bd_dev
regardless of whether the buffer head has a pointer to a block_device
structure.&lt;/p&gt;
&lt;p&gt;In the current implementation, nilfs_grab_buffer(), which grabs a buffer
to read (or create) a block of metadata, including b-tree node blocks,
does not set the block device, but instead does so only if the buffer is
not in the &amp;#34;uptodate&amp;#34; state for each of its caller block reading
functions.  However, if the uptodate flag is set on a folio/page, and the
buffer heads are detached from it by try_to_free_buffers(), and new buffer
heads are then attached by create_empty_buffers(), the uptodate flag may
be restored to each buffer without the block device being set to
bh-&amp;gt;b_bdev, and mark_buffer_dirty() may be called later in that state,
resulting in the bug mentioned above.&lt;/p&gt;
&lt;p&gt;Fix this issue by making nilfs_grab_buffer() always set the block device
of the super block structure to the buffer head, regardless of the state
of the buffer&amp;#39;s uptodate flag.&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;nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint&lt;/p&gt;
&lt;p&gt;When using the &amp;#34;block:block_dirty_buffer&amp;#34; tracepoint, mark_buffer_dirty()
may cause a NULL pointer dereference, or a general protection fault when
KASAN is enabled.&lt;/p&gt;
&lt;p&gt;This happens because, since the tracepoint was added in
mark_buffer_dirty(), it references the dev_t member bh-&amp;gt;b_bdev-&amp;gt;bd_dev
regardless of whether the buffer head has a pointer to a block_device
structure.&lt;/p&gt;
&lt;p&gt;In the current implementation, nilfs_grab_buffer(), which grabs a buffer
to read (or create) a block of metadata, including b-tree node blocks,
does not set the block device, but instead does so only if the buffer is
not in the &amp;#34;uptodate&amp;#34; state for each of its caller block reading
functions.  However, if the uptodate flag is set on a folio/page, and the
buffer heads are detached from it by try_to_free_buffers(), and new buffer
heads are then attached by create_empty_buffers(), the uptodate flag may
be restored to each buffer without the block device being set to
bh-&amp;gt;b_bdev, and mark_buffer_dirty() may be called later in that state,
resulting in the bug mentioned above.&lt;/p&gt;
&lt;p&gt;Fix this issue by making nilfs_grab_buffer() always set the block device
of the super block structure to the buffer head, regardless of the state
of the buffer&amp;#39;s uptodate flag.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-53130</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>
