<?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 03:56:15 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-38605</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-38605</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-38605</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0578 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0578</link>
      <description>certfr-2024-avi-0578</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0578</guid>
    </item>
    <item>
      <title>OESA-2024-1766 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1766</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer&#13;
&#13;
The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the
maximum transfer length and the size of the transfer buffer. As such, it
does not account for the 4 bytes of header that prepends the SPI data
frame. This can result in out-of-bounds accesses and was confirmed with
KASAN.&#13;
&#13;
Introduce SPI_HDRSIZE to account for the header and use to allocate the
transfer buffer.(CVE-2024-36477)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
net: fix out-of-bounds access in ops_init&#13;
&#13;
net_alloc_generic is called by net_alloc, which is called without any
locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It
is read twice, first to allocate an array, then to set s.len, which is
later used to limit the bounds of the array access.&#13;
&#13;
It is possible that the array is allocated and another thread is
registering a new pernet ops, increments max_gen_ptrs, which is then used
to set s.len with a larger than allocated length for the variable array.&#13;
&#13;
Fix it by reading max_gen_ptrs only once in net_alloc_generic. If
max_gen_ptrs is later incremented, it will be caught in net_assign_generic.(CVE-2024-36883)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
gpiolib: cdev: fix uninitialised kfif…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer&#13;
&#13;
The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the
maximum transfer length and the size of the transfer buffer. As such, it
does not account for the 4 bytes of header that prepends the SPI data
frame. This can result in out-of-bounds accesses and was confirmed with
KASAN.&#13;
&#13;
Introduce SPI_HDRSIZE to account for the header and use to allocate the
transfer buffer.(CVE-2024-36477)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
net: fix out-of-bounds access in ops_init&#13;
&#13;
net_alloc_generic is called by net_alloc, which is called without any
locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It
is read twice, first to allocate an array, then to set s.len, which is
later used to limit the bounds of the array access.&#13;
&#13;
It is possible that the array is allocated and another thread is
registering a new pernet ops, increments max_gen_ptrs, which is then used
to set s.len with a larger than allocated length for the variable array.&#13;
&#13;
Fix it by reading max_gen_ptrs only once in net_alloc_generic. If
max_gen_ptrs is later incremented, it will be caught in net_assign_generic.(CVE-2024-36883)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
gpiolib: cdev: fix uninitialised kfif…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1766</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-38605</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38605</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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix NULL module pointer assignment at card init The commit 81033c6b584b (&amp;#34;ALSA: core: Warn on empty module&amp;#34;) introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with &amp;#39;#ifdef MODULE&amp;#39;.  This works in most cases, but the devils are always in details.  &amp;#34;MODULE&amp;#34; is defined when the target code (i.e. the sound core) is built as a module; but this doesn&amp;#39;t mean that the caller is also built-in or not.  Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it&amp;#39;s non-NULL, and card-&amp;gt;module remains as NULL.  This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal. For addressing the bug, move the assignment of card-&amp;gt;module again out of ifdef.  The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in. Note that we keep &amp;#39;ifdef MODULE&amp;#39; for WARN_ON(), otherwise it would lead to a false-positive NULL module check.  Admittedly it won&amp;#39;t catch perfectly, i.e. no check is performed when CONFIG_SND=y.  But, it&amp;#39;s no real problem as it&amp;#39;s only for debugging, and the condition is pretty rare.&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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix NULL module pointer assignment at card init The commit 81033c6b584b (&amp;#34;ALSA: core: Warn on empty module&amp;#34;) introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with &amp;#39;#ifdef MODULE&amp;#39;.  This works in most cases, but the devils are always in details.  &amp;#34;MODULE&amp;#34; is defined when the target code (i.e. the sound core) is built as a module; but this doesn&amp;#39;t mean that the caller is also built-in or not.  Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it&amp;#39;s non-NULL, and card-&amp;gt;module remains as NULL.  This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal. For addressing the bug, move the assignment of card-&amp;gt;module again out of ifdef.  The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in. Note that we keep &amp;#39;ifdef MODULE&amp;#39; for WARN_ON(), otherwise it would lead to a false-positive NULL module check.  Admittedly it won&amp;#39;t catch perfectly, i.e. no check is performed when CONFIG_SND=y.  But, it&amp;#39;s no real problem as it&amp;#39;s only for debugging, and the condition is pretty rare.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38605</guid>
    </item>
  </channel>
</rss>
