<?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 07:54:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52699 — sysv: don't call sb_bread() with pointers_lock held</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-52699</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;sysv: don&amp;#39;t call sb_bread() with pointers_lock held&lt;/p&gt;
&lt;p&gt;syzbot is reporting sleep in atomic context in SysV filesystem [1], for
sb_bread() is called with rw_spinlock held.&lt;/p&gt;
&lt;p&gt;A &amp;#34;write_lock(&amp;amp;pointers_lock) =&amp;gt; read_lock(&amp;amp;pointers_lock) deadlock&amp;#34; bug
and a &amp;#34;sb_bread() with write_lock(&amp;amp;pointers_lock)&amp;#34; bug were introduced by
&amp;#34;Replace BKL for chain locking with sysvfs-private rwlock&amp;#34; in Linux 2.5.12.&lt;/p&gt;
&lt;p&gt;Then, &amp;#34;[PATCH] err1-40: sysvfs locking fix&amp;#34; in Linux 2.6.8 fixed the
former bug by moving pointers_lock lock to the callers, but instead
introduced a &amp;#34;sb_bread() with read_lock(&amp;amp;pointers_lock)&amp;#34; bug (which made
this problem easier to hit).&lt;/p&gt;
&lt;p&gt;Al Viro suggested that why not to do like get_branch()/get_block()/
find_shared() in Minix filesystem does. And doing like that is almost a
revert of &amp;#34;[PATCH] err1-40: sysvfs locking fix&amp;#34; except that get_branch()
 from with find_shared() is called without write_lock(&amp;amp;pointers_lock).&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;sysv: don&amp;#39;t call sb_bread() with pointers_lock held&lt;/p&gt;
&lt;p&gt;syzbot is reporting sleep in atomic context in SysV filesystem [1], for
sb_bread() is called with rw_spinlock held.&lt;/p&gt;
&lt;p&gt;A &amp;#34;write_lock(&amp;amp;pointers_lock) =&amp;gt; read_lock(&amp;amp;pointers_lock) deadlock&amp;#34; bug
and a &amp;#34;sb_bread() with write_lock(&amp;amp;pointers_lock)&amp;#34; bug were introduced by
&amp;#34;Replace BKL for chain locking with sysvfs-private rwlock&amp;#34; in Linux 2.5.12.&lt;/p&gt;
&lt;p&gt;Then, &amp;#34;[PATCH] err1-40: sysvfs locking fix&amp;#34; in Linux 2.6.8 fixed the
former bug by moving pointers_lock lock to the callers, but instead
introduced a &amp;#34;sb_bread() with read_lock(&amp;amp;pointers_lock)&amp;#34; bug (which made
this problem easier to hit).&lt;/p&gt;
&lt;p&gt;Al Viro suggested that why not to do like get_branch()/get_block()/
find_shared() in Minix filesystem does. And doing like that is almost a
revert of &amp;#34;[PATCH] err1-40: sysvfs locking fix&amp;#34; except that get_branch()
 from with find_shared() is called without write_lock(&amp;amp;pointers_lock).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-52699</guid>
    </item>
    <item>
      <title>USN-6893-1 — linux, linux-azure, linux-gcp, linux-ibm, linux-intel, linux-lowlatency, linux-oem-6.8, linux-raspi vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-6893-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-azure, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-intel, Ubuntu:24.04:LTS: linux-lowlatency, Ubuntu:24.04:LTS: linux-oem-6.8, Ubuntu:24.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;It was discovered that a race condition existed in the Bluetooth subsystem
in the Linux kernel when modifying certain settings values through debugfs.
A privileged local attacker could use this to cause a denial of service.
(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)&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:
  - ARM64 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - Accessibility subsystem;
  - Android drivers;
  - Drivers core;
  - Bluetooth drivers;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Cryptographic API;
  - Buffer Sharing and Synchronization framework;
  - GPU drivers;
  - On-Chip Interconnect management framework;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - VMware VMCI Driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - Device tree and open firmware driver;
  - Chrome hardware platform drivers;
  - i.MX PM domains;
  - TI SCI PM domains driver;
  - S/390 drivers;
  - SCSI drivers;
  - SPI subsystem;
  - Thermal drivers;
  - TTY drivers;
  - USB subsystem;
  - Framebuffer layer;
  - BTRFS file system;
  - Network file system server daemon;
  - NILFS2 file system;
  - File systems infrastructure;
  - Pstore file system;
  - SMB…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-azure, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-intel, Ubuntu:24.04:LTS: linux-lowlatency, Ubuntu:24.04:LTS: linux-oem-6.8, Ubuntu:24.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;It was discovered that a race condition existed in the Bluetooth subsystem
in the Linux kernel when modifying certain settings values through debugfs.
A privileged local attacker could use this to cause a denial of service.
(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)&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:
  - ARM64 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - Accessibility subsystem;
  - Android drivers;
  - Drivers core;
  - Bluetooth drivers;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Cryptographic API;
  - Buffer Sharing and Synchronization framework;
  - GPU drivers;
  - On-Chip Interconnect management framework;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - VMware VMCI Driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - Device tree and open firmware driver;
  - Chrome hardware platform drivers;
  - i.MX PM domains;
  - TI SCI PM domains driver;
  - S/390 drivers;
  - SCSI drivers;
  - SPI subsystem;
  - Thermal drivers;
  - TTY drivers;
  - USB subsystem;
  - Framebuffer layer;
  - BTRFS file system;
  - Network file system server daemon;
  - NILFS2 file system;
  - File systems infrastructure;
  - Pstore file system;
  - SMB…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-6893-1</guid>
    </item>
  </channel>
</rss>
