<?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://vulnerability.circl.lu</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>Sun, 11 Oct 2026 03:17:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-38599 — jffs2: prevent xattr node from overflowing the eraseblock</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-38599</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;jffs2: prevent xattr node from overflowing the eraseblock&lt;/p&gt;
&lt;p&gt;Add a check to make sure that the requested xattr node size is no larger
than the eraseblock minus the cleanmarker.&lt;/p&gt;
&lt;p&gt;Unlike the usual inode nodes, the xattr nodes aren&amp;#39;t split into parts
and spread across multiple eraseblocks, which means that a xattr node
must not occupy more than one eraseblock. If the requested xattr value is
too large, the xattr node can spill onto the next eraseblock, overwriting
the nodes and causing errors such as:&lt;/p&gt;
&lt;p&gt;jffs2: argh. node added in wrong place at 0x0000b050(2)
jffs2: nextblock 0x0000a000, expected at 0000b00c
jffs2: error: (823) do_verify_xattr_datum: node CRC failed at 0x01e050,
read=0xfc892c93, calc=0x000000
jffs2: notice: (823) jffs2_get_inode_nodes: Node header CRC failed
at 0x01e00c. {848f,2fc4,0fef511f,59a3d171}
jffs2: Node at 0x0000000c with length 0x00001044 would run over the
end of the erase block
jffs2: Perhaps the file system was created with the wrong erase size?
jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found
at 0x00000010: 0x1044 instead&lt;/p&gt;
&lt;p&gt;This breaks the filesystem and can lead to KASAN crashes such as:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in jffs2_sum_add_kvec+0x125e/0x15d0
Read of size 4 at addr ffff88802c31e914 by task repro/830
CPU: 0 PID: 830 Comm: repro Not tainted 6.9.0-rc3+ #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS Arch Linux 1.16.3-1-1 04/01/2014
Call Trace:
 &amp;lt;…&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;jffs2: prevent xattr node from overflowing the eraseblock&lt;/p&gt;
&lt;p&gt;Add a check to make sure that the requested xattr node size is no larger
than the eraseblock minus the cleanmarker.&lt;/p&gt;
&lt;p&gt;Unlike the usual inode nodes, the xattr nodes aren&amp;#39;t split into parts
and spread across multiple eraseblocks, which means that a xattr node
must not occupy more than one eraseblock. If the requested xattr value is
too large, the xattr node can spill onto the next eraseblock, overwriting
the nodes and causing errors such as:&lt;/p&gt;
&lt;p&gt;jffs2: argh. node added in wrong place at 0x0000b050(2)
jffs2: nextblock 0x0000a000, expected at 0000b00c
jffs2: error: (823) do_verify_xattr_datum: node CRC failed at 0x01e050,
read=0xfc892c93, calc=0x000000
jffs2: notice: (823) jffs2_get_inode_nodes: Node header CRC failed
at 0x01e00c. {848f,2fc4,0fef511f,59a3d171}
jffs2: Node at 0x0000000c with length 0x00001044 would run over the
end of the erase block
jffs2: Perhaps the file system was created with the wrong erase size?
jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found
at 0x00000010: 0x1044 instead&lt;/p&gt;
&lt;p&gt;This breaks the filesystem and can lead to KASAN crashes such as:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in jffs2_sum_add_kvec+0x125e/0x15d0
Read of size 4 at addr ffff88802c31e914 by task repro/830
CPU: 0 PID: 830 Comm: repro Not tainted 6.9.0-rc3+ #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS Arch Linux 1.16.3-1-1 04/01/2014
Call Trace:
 &amp;lt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-38599</guid>
    </item>
    <item>
      <title>USN-6949-1 — linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-nvidia, linux-nvidia-6.8 vulnerabilities</title>
      <link>https://vulnerability.circl.lu/vuln/usn-6949-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-nvidia&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;
  - M68K architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Accessibility subsystem;
  - Bluetooth drivers;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Macintosh device drivers;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - MMC subsystem;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Device tree and open firmware driver;
  - HiSilicon SoC PMU drivers;
  - PHY drivers;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Thermal drivers;
  - Userspace I/O drivers;
  - USB subsystem;
  - DesignWare USB3 driver;
  - ACRN Hypervisor Service Module driver;
  - Virtio drivers;
  - 9P distributed file system;
  - BTRFS file system;
  - eCrypt file system;
  - EROFS file system;
  - File systems infrastructure;
  - GF…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-nvidia&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;
  - M68K architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Accessibility subsystem;
  - Bluetooth drivers;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Macintosh device drivers;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - MMC subsystem;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Device tree and open firmware driver;
  - HiSilicon SoC PMU drivers;
  - PHY drivers;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Thermal drivers;
  - Userspace I/O drivers;
  - USB subsystem;
  - DesignWare USB3 driver;
  - ACRN Hypervisor Service Module driver;
  - Virtio drivers;
  - 9P distributed file system;
  - BTRFS file system;
  - eCrypt file system;
  - EROFS file system;
  - File systems infrastructure;
  - GF…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-6949-1</guid>
    </item>
  </channel>
</rss>
