<?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:54 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-39475</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-39475</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-39475</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0610 — 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-0610</link>
      <description>certfr-2024-avi-0610</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0610</guid>
    </item>
    <item>
      <title>OESA-2024-1941 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1941</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
clk: sunxi-ng: Unregister clocks/resets when unbinding&#13;
&#13;
Currently, unbinding a CCU driver unmaps the device&amp;amp;apos;s MMIO region, while
leaving its clocks/resets and their providers registered. This can cause
a page fault later when some clock operation tries to perform MMIO. Fix
this by separating the CCU initialization from the memory allocation,
and then using a devres callback to unregister the clocks and resets.&#13;
&#13;
This also fixes a memory leak of the `struct ccu_reset`, and uses the
correct owner (the specific platform driver) for the clocks and resets.&#13;
&#13;
Early OF clock providers are never unregistered, and limited error
handling is possible, so they are mostly unchanged. The error reporting
is made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR&#13;
&#13;
In some case, the GDDV returns a package with a buffer which has
zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).&#13;
&#13;
Then the data_vault_read() got NULL point dereference problem when
accessing the 0x10 value in data_vault.&#13;
&#13;
[   71.024560] BUG: kernel NULL pointer dereference, address:
0000000000000010&#13;
&#13;
This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or
NULL value…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
clk: sunxi-ng: Unregister clocks/resets when unbinding&#13;
&#13;
Currently, unbinding a CCU driver unmaps the device&amp;amp;apos;s MMIO region, while
leaving its clocks/resets and their providers registered. This can cause
a page fault later when some clock operation tries to perform MMIO. Fix
this by separating the CCU initialization from the memory allocation,
and then using a devres callback to unregister the clocks and resets.&#13;
&#13;
This also fixes a memory leak of the `struct ccu_reset`, and uses the
correct owner (the specific platform driver) for the clocks and resets.&#13;
&#13;
Early OF clock providers are never unregistered, and limited error
handling is possible, so they are mostly unchanged. The error reporting
is made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR&#13;
&#13;
In some case, the GDDV returns a package with a buffer which has
zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).&#13;
&#13;
Then the data_vault_read() got NULL point dereference problem when
accessing the 0x10 value in data_vault.&#13;
&#13;
[   71.024560] BUG: kernel NULL pointer dereference, address:
0000000000000010&#13;
&#13;
This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or
NULL value…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1941</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-39475</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-39475</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 135 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fbdev: savage: Handle err return when savagefb_check_var failed The commit 04e5eac8f3ab(&amp;#34;fbdev: savage: Error out if pixclock equals zero&amp;#34;) checks the value of pixclock to avoid divide-by-zero error. However the function savagefb_probe doesn&amp;#39;t handle the error return of savagefb_check_var. When pixclock is 0, it will cause divide-by-zero error.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 135 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fbdev: savage: Handle err return when savagefb_check_var failed The commit 04e5eac8f3ab(&amp;#34;fbdev: savage: Error out if pixclock equals zero&amp;#34;) checks the value of pixclock to avoid divide-by-zero error. However the function savagefb_probe doesn&amp;#39;t handle the error return of savagefb_check_var. When pixclock is 0, it will cause divide-by-zero error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-39475</guid>
    </item>
  </channel>
</rss>
