<?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>Sun, 04 Oct 2026 15:19:48 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-01800</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-01800</link>
      <description>bdu:2024-01800</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-01800</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0242 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de SUSE&lt;/span&gt;. Certaines d'en…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0242</link>
      <description>certfr-2024-avi-0242</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0242</guid>
    </item>
    <item>
      <title>EUVD-2026-344371</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344371</link>
      <description>EUVD-2026-344371</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344371</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47060</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47060</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: Stop looking for coalesced MMIO zones if the bus is destroyed&lt;/p&gt;
&lt;p&gt;Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()
fails to allocate memory for the new instance of the bus.  If it can&amp;#39;t
instantiate a new bus, unregister_dev() destroys all devices _except_ the
target device.   But, it doesn&amp;#39;t tell the caller that it obliterated the
bus and invoked the destructor for all devices that were on the bus.  In
the coalesced MMIO case, this can result in a deleted list entry
dereference due to attempting to continue iterating on coalesced_zones
after future entries (in the walk) have been deleted.&lt;/p&gt;
&lt;p&gt;Opportunistically add curly braces to the for-loop, which encompasses
many lines but sneaks by without braces due to the guts being a single
if statement.&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;KVM: Stop looking for coalesced MMIO zones if the bus is destroyed&lt;/p&gt;
&lt;p&gt;Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()
fails to allocate memory for the new instance of the bus.  If it can&amp;#39;t
instantiate a new bus, unregister_dev() destroys all devices _except_ the
target device.   But, it doesn&amp;#39;t tell the caller that it obliterated the
bus and invoked the destructor for all devices that were on the bus.  In
the coalesced MMIO case, this can result in a deleted list entry
dereference due to attempting to continue iterating on coalesced_zones
after future entries (in the walk) have been deleted.&lt;/p&gt;
&lt;p&gt;Opportunistically add curly braces to the for-loop, which encompasses
many lines but sneaks by without braces due to the guts being a single
if statement.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47060</guid>
    </item>
    <item>
      <title>GHSA-6x38-gwgp-2pcm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6x38-gwgp-2pcm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: Stop looking for coalesced MMIO zones if the bus is destroyed&lt;/p&gt;
&lt;p&gt;Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()
fails to allocate memory for the new instance of the bus.  If it can&amp;#39;t
instantiate a new bus, unregister_dev() destroys all devices _except_ the
target device.   But, it doesn&amp;#39;t tell the caller that it obliterated the
bus and invoked the destructor for all devices that were on the bus.  In
the coalesced MMIO case, this can result in a deleted list entry
dereference due to attempting to continue iterating on coalesced_zones
after future entries (in the walk) have been deleted.&lt;/p&gt;
&lt;p&gt;Opportunistically add curly braces to the for-loop, which encompasses
many lines but sneaks by without braces due to the guts being a single
if statement.&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;KVM: Stop looking for coalesced MMIO zones if the bus is destroyed&lt;/p&gt;
&lt;p&gt;Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()
fails to allocate memory for the new instance of the bus.  If it can&amp;#39;t
instantiate a new bus, unregister_dev() destroys all devices _except_ the
target device.   But, it doesn&amp;#39;t tell the caller that it obliterated the
bus and invoked the destructor for all devices that were on the bus.  In
the coalesced MMIO case, this can result in a deleted list entry
dereference due to attempting to continue iterating on coalesced_zones
after future entries (in the walk) have been deleted.&lt;/p&gt;
&lt;p&gt;Opportunistically add curly braces to the for-loop, which encompasses
many lines but sneaks by without braces due to the guts being a single
if statement.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6x38-gwgp-2pcm</guid>
    </item>
    <item>
      <title>gsd-2021-47060</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-47060</link>
      <description>gsd-2021-47060</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-47060</guid>
    </item>
    <item>
      <title>OESA-2024-1483 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1483</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;
i2c: img-scb: fix reference leak when pm_runtime_get_sync fails&#13;
&#13;
The PM reference count is not expected to be incremented on
return in functions img_i2c_xfer and img_i2c_init.&#13;
&#13;
However, pm_runtime_get_sync will increment the PM reference
count even failed. Forgetting to putting operation will result
in a reference leak here.&#13;
&#13;
Replace it with pm_runtime_resume_and_get to keep usage
counter balanced.(CVE-2020-36783)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
kyber: fix out of bounds access when preempted&#13;
&#13;
__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and
passes the hctx to -&amp;amp;gt;bio_merge(). kyber_bio_merge() then gets the ctx
for the current CPU again and uses that to get the corresponding Kyber
context in the passed hctx. However, the thread may be preempted between
the two calls to blk_mq_get_ctx(), and the ctx returned the second time
may no longer correspond to the passed hctx. This &amp;amp;quot;works&amp;amp;quot; accidentally
most of the time, but it can cause us to read garbage if the second ctx
came from an hctx with more ctx&amp;amp;apos;s than the first one (i.e., if
ctx-&amp;amp;gt;index_hw[hctx-&amp;amp;gt;type] &amp;amp;gt; hctx-&amp;amp;gt;nr_ctx).&#13;
&#13;
This manifested as this UBSAN array index out of bounds error reported
by Jakub:&#13;
&#13;
UBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9
index 1…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;
i2c: img-scb: fix reference leak when pm_runtime_get_sync fails&#13;
&#13;
The PM reference count is not expected to be incremented on
return in functions img_i2c_xfer and img_i2c_init.&#13;
&#13;
However, pm_runtime_get_sync will increment the PM reference
count even failed. Forgetting to putting operation will result
in a reference leak here.&#13;
&#13;
Replace it with pm_runtime_resume_and_get to keep usage
counter balanced.(CVE-2020-36783)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
kyber: fix out of bounds access when preempted&#13;
&#13;
__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and
passes the hctx to -&amp;amp;gt;bio_merge(). kyber_bio_merge() then gets the ctx
for the current CPU again and uses that to get the corresponding Kyber
context in the passed hctx. However, the thread may be preempted between
the two calls to blk_mq_get_ctx(), and the ctx returned the second time
may no longer correspond to the passed hctx. This &amp;amp;quot;works&amp;amp;quot; accidentally
most of the time, but it can cause us to read garbage if the second ctx
came from an hctx with more ctx&amp;amp;apos;s than the first one (i.e., if
ctx-&amp;amp;gt;index_hw[hctx-&amp;amp;gt;type] &amp;amp;gt; hctx-&amp;amp;gt;nr_ctx).&#13;
&#13;
This manifested as this UBSAN array index out of bounds error reported
by Jakub:&#13;
&#13;
UBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9
index 1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1483</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:0856-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:0856-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:0856-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47060</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47060</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 95 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: Stop looking for coalesced MMIO zones if the bus is destroyed Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev() fails to allocate memory for the new instance of the bus.  If it can&amp;#39;t instantiate a new bus, unregister_dev() destroys all devices _except_ the target device.   But, it doesn&amp;#39;t tell the caller that it obliterated the bus and invoked the destructor for all devices that were on the bus.  In the coalesced MMIO case, this can result in a deleted list entry dereference due to attempting to continue iterating on coalesced_zones after future entries (in the walk) have been deleted. Opportunistically add curly braces to the for-loop, which encompasses many lines but sneaks by without braces due to the guts being a single if statement.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 95 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: Stop looking for coalesced MMIO zones if the bus is destroyed Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev() fails to allocate memory for the new instance of the bus.  If it can&amp;#39;t instantiate a new bus, unregister_dev() destroys all devices _except_ the target device.   But, it doesn&amp;#39;t tell the caller that it obliterated the bus and invoked the destructor for all devices that were on the bus.  In the coalesced MMIO case, this can result in a deleted list entry dereference due to attempting to continue iterating on coalesced_zones after future entries (in the walk) have been deleted. Opportunistically add curly braces to the for-loop, which encompasses many lines but sneaks by without braces due to the guts being a single if statement.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47060</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0527 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0527</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand zu verursachen und einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand zu verursachen und 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-0527</guid>
    </item>
  </channel>
</rss>
