<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 04:06:32 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-27005</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-27005</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2024-27005</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0611 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0611</link>
      <description>certfr-2024-avi-0611</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0611</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-27005</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-27005</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: interconnect: Don&amp;#39;t access req_list while it&amp;#39;s being manipulated 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. 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(). Example A:   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; Example B:   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_head(...…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: interconnect: Don&amp;#39;t access req_list while it&amp;#39;s being manipulated 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. 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(). Example A:   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; Example B:   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_head(...…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-27005</guid>
    </item>
  </channel>
</rss>
