<?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 17:08:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-01540</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-01540</link>
      <description>bdu:2026-01540</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-01540</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0212 — 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://cve.radiocsirt.org/vuln/certfr-2025-avi-0212</link>
      <description>certfr-2025-avi-0212</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0212</guid>
    </item>
    <item>
      <title>EUVD-2026-351806</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-351806</link>
      <description>EUVD-2026-351806</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-351806</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49135</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49135</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Fix memory leak&lt;/p&gt;
&lt;p&gt;[why]
Resource release is needed on the error handling path
to prevent memory leak.&lt;/p&gt;
&lt;p&gt;[how]
Fix this by adding kfree on the error handling path.&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/amd/display: Fix memory leak&lt;/p&gt;
&lt;p&gt;[why]
Resource release is needed on the error handling path
to prevent memory leak.&lt;/p&gt;
&lt;p&gt;[how]
Fix this by adding kfree on the error handling path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49135</guid>
    </item>
    <item>
      <title>GHSA-8v22-4px4-6c2p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8v22-4px4-6c2p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Fix memory leak&lt;/p&gt;
&lt;p&gt;[why]
Resource release is needed on the error handling path
to prevent memory leak.&lt;/p&gt;
&lt;p&gt;[how]
Fix this by adding kfree on the error handling path.&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/amd/display: Fix memory leak&lt;/p&gt;
&lt;p&gt;[why]
Resource release is needed on the error handling path
to prevent memory leak.&lt;/p&gt;
&lt;p&gt;[how]
Fix this by adding kfree on the error handling path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8v22-4px4-6c2p</guid>
    </item>
    <item>
      <title>OESA-2025-1337 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1337</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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Fix memory leak&lt;/p&gt;
&lt;p&gt;[why]
Resource release is needed on the error handling path
to prevent memory leak.&lt;/p&gt;
&lt;p&gt;[how]
Fix this by adding kfree on the error handling path.(CVE-2022-49135)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;block: fix rq-qos breakage from skipping rq_qos_done_bio()&lt;/p&gt;
&lt;p&gt;a647a524a467 (&amp;amp;quot;block: don&amp;amp;apos;t call rq_qos_ops-&amp;amp;gt;done_bio if the bio isn&amp;amp;apos;t
tracked&amp;amp;quot;) made bio_endio() skip rq_qos_done_bio() if BIO_TRACKED is not set.
While this fixed a potential oops, it also broke blk-iocost by skipping the
done_bio callback for merged bios.&lt;/p&gt;
&lt;p&gt;Before, whether a bio goes through rq_qos_throttle() or rq_qos_merge(),
rq_qos_done_bio() would be called on the bio on completion with BIO_TRACKED
distinguishing the former from the latter. rq_qos_done_bio() is not called
for bios which wenth through rq_qos_merge(). This royally confuses
blk-iocost as the merged bios never finish and are considered perpetually
in-flight.&lt;/p&gt;
&lt;p&gt;One reliably reproducible failure mode is an intermediate cgroup geting
stuck active preventing its children from being activated due to the
leaf-only rule, leading to loss of control. The following is from
resctl-bench protection scenario which emulates isolating a web server like
workload from a memory bomb run on an iocost configuration which should
yield a reasonable…&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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Fix memory leak&lt;/p&gt;
&lt;p&gt;[why]
Resource release is needed on the error handling path
to prevent memory leak.&lt;/p&gt;
&lt;p&gt;[how]
Fix this by adding kfree on the error handling path.(CVE-2022-49135)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;block: fix rq-qos breakage from skipping rq_qos_done_bio()&lt;/p&gt;
&lt;p&gt;a647a524a467 (&amp;amp;quot;block: don&amp;amp;apos;t call rq_qos_ops-&amp;amp;gt;done_bio if the bio isn&amp;amp;apos;t
tracked&amp;amp;quot;) made bio_endio() skip rq_qos_done_bio() if BIO_TRACKED is not set.
While this fixed a potential oops, it also broke blk-iocost by skipping the
done_bio callback for merged bios.&lt;/p&gt;
&lt;p&gt;Before, whether a bio goes through rq_qos_throttle() or rq_qos_merge(),
rq_qos_done_bio() would be called on the bio on completion with BIO_TRACKED
distinguishing the former from the latter. rq_qos_done_bio() is not called
for bios which wenth through rq_qos_merge(). This royally confuses
blk-iocost as the merged bios never finish and are considered perpetually
in-flight.&lt;/p&gt;
&lt;p&gt;One reliably reproducible failure mode is an intermediate cgroup geting
stuck active preventing its children from being activated due to the
leaf-only rule, leading to loss of control. The following is from
resctl-bench protection scenario which emulates isolating a web server like
workload from a memory bomb run on an iocost configuration which should
yield a reasonable…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1337</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0834-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0834-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-2025:0834-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49135</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49135</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 139 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak [why] Resource release is needed on the error handling path to prevent memory leak. [how] Fix this by adding kfree on the error handling path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 139 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak [why] Resource release is needed on the error handling path to prevent memory leak. [how] Fix this by adding kfree on the error handling path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49135</guid>
    </item>
  </channel>
</rss>
