<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 03:27:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71067 — ntfs: set dummy blocksize to read boot_block when mounting</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-71067</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;ntfs: set dummy blocksize to read boot_block when mounting&lt;/p&gt;
&lt;p&gt;When mounting, sb-&amp;gt;s_blocksize is used to read the boot_block without
being defined or validated. Set a dummy blocksize before attempting to
read the boot_block.&lt;/p&gt;
&lt;p&gt;The issue can be triggered with the following syz reproducer:&lt;/p&gt;
&lt;p&gt;mkdirat(0xffffffffffffff9c, &amp;amp;(0x7f0000000080)=&amp;#39;./file1\x00&amp;#39;, 0x0)
  r4 = openat$nullb(0xffffffffffffff9c, &amp;amp;(0x7f0000000040), 0x121403, 0x0)
  ioctl$FS_IOC_SETFLAGS(r4, 0x40081271, &amp;amp;(0x7f0000000980)=0x4000)
  mount(&amp;amp;(0x7f0000000140)=@nullb, &amp;amp;(0x7f0000000040)=&amp;#39;./cgroup\x00&amp;#39;,
        &amp;amp;(0x7f0000000000)=&amp;#39;ntfs3\x00&amp;#39;, 0x2208004, 0x0)
  syz_clone(0x88200200, 0x0, 0x0, 0x0, 0x0, 0x0)&lt;/p&gt;
&lt;p&gt;Here, the ioctl sets the bdev block size to 16384. During mount,
get_tree_bdev_flags() calls sb_set_blocksize(sb, block_size(bdev)),
but since block_size(bdev) &amp;gt; PAGE_SIZE, sb_set_blocksize() leaves
sb-&amp;gt;s_blocksize at zero.&lt;/p&gt;
&lt;p&gt;Later, ntfs_init_from_boot() attempts to read the boot_block while
sb-&amp;gt;s_blocksize is still zero, which triggers the bug.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: changed comment style, added
return value handling]&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;ntfs: set dummy blocksize to read boot_block when mounting&lt;/p&gt;
&lt;p&gt;When mounting, sb-&amp;gt;s_blocksize is used to read the boot_block without
being defined or validated. Set a dummy blocksize before attempting to
read the boot_block.&lt;/p&gt;
&lt;p&gt;The issue can be triggered with the following syz reproducer:&lt;/p&gt;
&lt;p&gt;mkdirat(0xffffffffffffff9c, &amp;amp;(0x7f0000000080)=&amp;#39;./file1\x00&amp;#39;, 0x0)
  r4 = openat$nullb(0xffffffffffffff9c, &amp;amp;(0x7f0000000040), 0x121403, 0x0)
  ioctl$FS_IOC_SETFLAGS(r4, 0x40081271, &amp;amp;(0x7f0000000980)=0x4000)
  mount(&amp;amp;(0x7f0000000140)=@nullb, &amp;amp;(0x7f0000000040)=&amp;#39;./cgroup\x00&amp;#39;,
        &amp;amp;(0x7f0000000000)=&amp;#39;ntfs3\x00&amp;#39;, 0x2208004, 0x0)
  syz_clone(0x88200200, 0x0, 0x0, 0x0, 0x0, 0x0)&lt;/p&gt;
&lt;p&gt;Here, the ioctl sets the bdev block size to 16384. During mount,
get_tree_bdev_flags() calls sb_set_blocksize(sb, block_size(bdev)),
but since block_size(bdev) &amp;gt; PAGE_SIZE, sb_set_blocksize() leaves
sb-&amp;gt;s_blocksize at zero.&lt;/p&gt;
&lt;p&gt;Later, ntfs_init_from_boot() attempts to read the boot_block while
sb-&amp;gt;s_blocksize is still zero, which triggers the bug.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: changed comment style, added
return value handling]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-71067</guid>
    </item>
    <item>
      <title>USN-8177-1 — linux, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8177-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: linux, Ubuntu:25.10: linux-realtime&lt;/p&gt;
&lt;p&gt;Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo
Rizzo discovered that some AMD Zen processors did not properly verify the
signature of CPU microcode. This flaw is known as EntrySign. A privileged
attacker could possibly use this issue to cause load malicious CPU
microcode causing loss of integrity and confidentiality.
(CVE-2024-36347)&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:
  - MIPS architecture;
  - PowerPC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - GPU drivers;
  - Hardware monitoring drivers;
  - Intel Trace Hub HW tracing drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - PA-RISC drivers;
  - Chrome hardware platform drivers;
  - x86 platform drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - TCM subsystem;
  - Freescale USB OTG Transceiver Driver;
  - USB Type-C Connector System Software Interface driver;
  - Watchdog drivers;
  - BTRFS file sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: linux, Ubuntu:25.10: linux-realtime&lt;/p&gt;
&lt;p&gt;Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo
Rizzo discovered that some AMD Zen processors did not properly verify the
signature of CPU microcode. This flaw is known as EntrySign. A privileged
attacker could possibly use this issue to cause load malicious CPU
microcode causing loss of integrity and confidentiality.
(CVE-2024-36347)&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:
  - MIPS architecture;
  - PowerPC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - GPU drivers;
  - Hardware monitoring drivers;
  - Intel Trace Hub HW tracing drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - PA-RISC drivers;
  - Chrome hardware platform drivers;
  - x86 platform drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - TCM subsystem;
  - Freescale USB OTG Transceiver Driver;
  - USB Type-C Connector System Software Interface driver;
  - Watchdog drivers;
  - BTRFS file sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8177-1</guid>
    </item>
  </channel>
</rss>
