<?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>Sat, 03 Oct 2026 11:11:58 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07484</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07484</link>
      <description>bdu:2024-07484</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07484</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-41011</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-41011</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://cve.radiocsirt.org/vuln/bell-cve-2024-41011</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0667 — 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://cve.radiocsirt.org/vuln/certfr-2024-avi-0667</link>
      <description>certfr-2024-avi-0667</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0667</guid>
    </item>
    <item>
      <title>EUVD-2026-345905</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345905</link>
      <description>EUVD-2026-345905</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345905</guid>
    </item>
    <item>
      <title>fkie_cve-2024-41011</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-41011</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdkfd: don&amp;#39;t allow mapping the MMIO HDP page with large pages&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t get the right offset in that case.  The GPU has
an unused 4K area of the register BAR space into which you can
remap registers.  We remap the HDP flush registers into this
space to allow userspace (CPU or GPU) to flush the HDP when it
updates VRAM.  However, on systems with &amp;gt;4K pages, we end up
exposing PAGE_SIZE of MMIO space.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdkfd: don&amp;#39;t allow mapping the MMIO HDP page with large pages&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t get the right offset in that case.  The GPU has
an unused 4K area of the register BAR space into which you can
remap registers.  We remap the HDP flush registers into this
space to allow userspace (CPU or GPU) to flush the HDP when it
updates VRAM.  However, on systems with &amp;gt;4K pages, we end up
exposing PAGE_SIZE of MMIO space.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-41011</guid>
    </item>
    <item>
      <title>GHSA-fv42-492h-89pj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fv42-492h-89pj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdkfd: don&amp;#39;t allow mapping the MMIO HDP page with large pages&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t get the right offset in that case.  The GPU has
an unused 4K area of the register BAR space into which you can
remap registers.  We remap the HDP flush registers into this
space to allow userspace (CPU or GPU) to flush the HDP when it
updates VRAM.  However, on systems with &amp;gt;4K pages, we end up
exposing PAGE_SIZE of MMIO space.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdkfd: don&amp;#39;t allow mapping the MMIO HDP page with large pages&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t get the right offset in that case.  The GPU has
an unused 4K area of the register BAR space into which you can
remap registers.  We remap the HDP flush registers into this
space to allow userspace (CPU or GPU) to flush the HDP when it
updates VRAM.  However, on systems with &amp;gt;4K pages, we end up
exposing PAGE_SIZE of MMIO space.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fv42-492h-89pj</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-41011 — drm/amdkfd: don't allow mapping the MMIO HDP page with large pages</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-41011</link>
      <description>msrc_CVE-2024-41011</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-41011</guid>
    </item>
    <item>
      <title>OESA-2024-1941 — kernel security update</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/oesa-2024-1941</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2802-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2802-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:2802-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-41011</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41011</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 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: don&amp;#39;t allow mapping the MMIO HDP page with large pages We don&amp;#39;t get the right offset in that case.  The GPU has an unused 4K area of the register BAR space into which you can remap registers.  We remap the HDP flush registers into this space to allow userspace (CPU or GPU) to flush the HDP when it updates VRAM.  However, on systems with &amp;gt;4K pages, we end up exposing PAGE_SIZE of MMIO space.&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 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: don&amp;#39;t allow mapping the MMIO HDP page with large pages We don&amp;#39;t get the right offset in that case.  The GPU has an unused 4K area of the register BAR space into which you can remap registers.  We remap the HDP flush registers into this space to allow userspace (CPU or GPU) to flush the HDP when it updates VRAM.  However, on systems with &amp;gt;4K pages, we end up exposing PAGE_SIZE of MMIO space.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41011</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1661 — Linux Kernel: Schwachstelle ermöglicht nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1661</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1661</guid>
    </item>
  </channel>
</rss>
