<?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>Mon, 12 Oct 2026 07:53:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-27005 — interconnect: Don't access req_list while it's being manipulated</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-27005</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;interconnect: Don&amp;#39;t access req_list while it&amp;#39;s being manipulated&lt;/p&gt;
&lt;p&gt;The icc_lock mutex was split into separate icc_lock and icc_bw_lock
mutexes in [1] to avoid lockdep splats. However, this didn&amp;#39;t adequately
protect access to icc_node::req_list.&lt;/p&gt;
&lt;p&gt;The icc_set_bw() function will eventually iterate over req_list while
only holding icc_bw_lock, but req_list can be modified while only
holding icc_lock. This causes races between icc_set_bw(), of_icc_get(),
and icc_put().&lt;/p&gt;
&lt;p&gt;Example A:&lt;/p&gt;
&lt;p&gt;CPU0                               CPU1
  ----                               ----
  icc_set_bw(path_a)
    mutex_lock(&amp;amp;icc_bw_lock);
                                     icc_put(path_b)
                                       mutex_lock(&amp;amp;icc_lock);
    aggregate_requests()
      hlist_for_each_entry(r, ...
                                       hlist_del(...
        &amp;lt;r = invalid pointer&amp;gt;&lt;/p&gt;
&lt;p&gt;Example B:&lt;/p&gt;
&lt;p&gt;CPU0                               CPU1
  ----                               ----
  icc_set_bw(path_a)
    mutex_lock(&amp;amp;icc_bw_lock);
                                     path_b = of_icc_get()
                                       of_icc_get_by_index()
                                         mutex_lock(&amp;amp;icc_lock);
                                         path_find()
                                           path_init()
    aggregate_requests()
      hlist_for_each_entry(r, ...
                                             hlist_add_hea…&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;interconnect: Don&amp;#39;t access req_list while it&amp;#39;s being manipulated&lt;/p&gt;
&lt;p&gt;The icc_lock mutex was split into separate icc_lock and icc_bw_lock
mutexes in [1] to avoid lockdep splats. However, this didn&amp;#39;t adequately
protect access to icc_node::req_list.&lt;/p&gt;
&lt;p&gt;The icc_set_bw() function will eventually iterate over req_list while
only holding icc_bw_lock, but req_list can be modified while only
holding icc_lock. This causes races between icc_set_bw(), of_icc_get(),
and icc_put().&lt;/p&gt;
&lt;p&gt;Example A:&lt;/p&gt;
&lt;p&gt;CPU0                               CPU1
  ----                               ----
  icc_set_bw(path_a)
    mutex_lock(&amp;amp;icc_bw_lock);
                                     icc_put(path_b)
                                       mutex_lock(&amp;amp;icc_lock);
    aggregate_requests()
      hlist_for_each_entry(r, ...
                                       hlist_del(...
        &amp;lt;r = invalid pointer&amp;gt;&lt;/p&gt;
&lt;p&gt;Example B:&lt;/p&gt;
&lt;p&gt;CPU0                               CPU1
  ----                               ----
  icc_set_bw(path_a)
    mutex_lock(&amp;amp;icc_bw_lock);
                                     path_b = of_icc_get()
                                       of_icc_get_by_index()
                                         mutex_lock(&amp;amp;icc_lock);
                                         path_find()
                                           path_init()
    aggregate_requests()
      hlist_for_each_entry(r, ...
                                             hlist_add_hea…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-27005</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>
