<?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 08:13:57 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-35902</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-35902</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-35902</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0527 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0527</link>
      <description>certfr-2024-avi-0527</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0527</guid>
    </item>
    <item>
      <title>OESA-2024-1765 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1765</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
spi: Fix deadlock when adding SPI controllers on SPI buses&#13;
&#13;
Currently we have a global spi_add_lock which we take when adding new
devices so that we can check that we&amp;amp;apos;re not trying to reuse a chip
select that&amp;amp;apos;s already controlled.  This means that if the SPI device is
itself a SPI controller and triggers the instantiation of further SPI
devices we trigger a deadlock as we try to register and instantiate
those devices while in the process of doing so for the parent controller
and hence already holding the global spi_add_lock.  Since we only care
about concurrency within a single SPI bus move the lock to be per
controller, avoiding the deadlock.&#13;
&#13;
This can be easily triggered in the case of spi-mux.(CVE-2021-47469)&#13;
&#13;
(CVE-2023-39180)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
hid: cp2112: Fix duplicate workqueue initialization&#13;
&#13;
Previously the cp2112 driver called INIT_DELAYED_WORK within
cp2112_gpio_irq_startup, resulting in duplicate initilizations of the
workqueue on subsequent IRQ startups following an initial request. This
resulted in a warning in set_work_data in workqueue.c, as well as a rare
NULL dereference within process_one_work in workqueue.c.&#13;
&#13;
Initialize the workqueue within _probe instead.(CVE-2023-52853)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolv…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
spi: Fix deadlock when adding SPI controllers on SPI buses&#13;
&#13;
Currently we have a global spi_add_lock which we take when adding new
devices so that we can check that we&amp;amp;apos;re not trying to reuse a chip
select that&amp;amp;apos;s already controlled.  This means that if the SPI device is
itself a SPI controller and triggers the instantiation of further SPI
devices we trigger a deadlock as we try to register and instantiate
those devices while in the process of doing so for the parent controller
and hence already holding the global spi_add_lock.  Since we only care
about concurrency within a single SPI bus move the lock to be per
controller, avoiding the deadlock.&#13;
&#13;
This can be easily triggered in the case of spi-mux.(CVE-2021-47469)&#13;
&#13;
(CVE-2023-39180)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
hid: cp2112: Fix duplicate workqueue initialization&#13;
&#13;
Previously the cp2112 driver called INIT_DELAYED_WORK within
cp2112_gpio_irq_startup, resulting in duplicate initilizations of the
workqueue on subsequent IRQ startups following an initial request. This
resulted in a warning in set_work_data in workqueue.c, as well as a rare
NULL dereference within process_one_work in workqueue.c.&#13;
&#13;
Initialize the workqueue within _probe instead.(CVE-2023-52853)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolv…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1765</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-35902</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35902</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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/rds: fix possible cp null dereference cp might be null, calling cp-&amp;gt;cp_conn would produce null dereference [Simon Horman adds:] Analysis: * cp is a parameter of __rds_rdma_map and is not reassigned. * The following call-sites pass a NULL cp argument to __rds_rdma_map()   - rds_get_mr()   - rds_get_mr_for_dest * Prior to the code above, the following assumes that cp may be NULL   (which is indicative, but could itself be unnecessary) 	trans_private = rs-&amp;gt;rs_transport-&amp;gt;get_mr( 		sg, nents, rs, &amp;amp;mr-&amp;gt;r_key, cp ? cp-&amp;gt;cp_conn : NULL, 		args-&amp;gt;vec.addr, args-&amp;gt;vec.bytes, 		need_odp ? ODP_ZEROBASED : ODP_NOT_NEEDED); * The code modified by this patch is guarded by IS_ERR(trans_private),   where trans_private is assigned as per the previous point in this analysis.   The only implementation of get_mr that I could locate is rds_ib_get_mr()   which can return an ERR_PTR if the conn (4th) argument is NULL. * ret is set to PTR_ERR(trans_private).   rds_ib_get_mr can return ERR_PTR(-ENODEV) if the conn (4th) argument is NULL.   Thus ret may be -ENODEV in which case the code in question will execute. Conclusion: * cp may be NULL at the point where this patch adds a check;   this patch does seem to address a possible bug&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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/rds: fix possible cp null dereference cp might be null, calling cp-&amp;gt;cp_conn would produce null dereference [Simon Horman adds:] Analysis: * cp is a parameter of __rds_rdma_map and is not reassigned. * The following call-sites pass a NULL cp argument to __rds_rdma_map()   - rds_get_mr()   - rds_get_mr_for_dest * Prior to the code above, the following assumes that cp may be NULL   (which is indicative, but could itself be unnecessary) 	trans_private = rs-&amp;gt;rs_transport-&amp;gt;get_mr( 		sg, nents, rs, &amp;amp;mr-&amp;gt;r_key, cp ? cp-&amp;gt;cp_conn : NULL, 		args-&amp;gt;vec.addr, args-&amp;gt;vec.bytes, 		need_odp ? ODP_ZEROBASED : ODP_NOT_NEEDED); * The code modified by this patch is guarded by IS_ERR(trans_private),   where trans_private is assigned as per the previous point in this analysis.   The only implementation of get_mr that I could locate is rds_ib_get_mr()   which can return an ERR_PTR if the conn (4th) argument is NULL. * ret is set to PTR_ERR(trans_private).   rds_ib_get_mr can return ERR_PTR(-ENODEV) if the conn (4th) argument is NULL.   Thus ret may be -ENODEV in which case the code in question will execute. Conclusion: * cp may be NULL at the point where this patch adds a check;   this patch does seem to address a possible bug&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35902</guid>
    </item>
  </channel>
</rss>
