<?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 04:29:18 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15769</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15769</link>
      <description>bdu:2025-15769</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15769</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38671</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38671</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-2025-38671</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0787 — 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-0787</link>
      <description>certfr-2025-avi-0787</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0787</guid>
    </item>
    <item>
      <title>EUVD-2026-314715</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314715</link>
      <description>EUVD-2026-314715</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314715</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38671</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38671</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i2c: qup: jump out of the loop in case of timeout&lt;/p&gt;
&lt;p&gt;Original logic only sets the return value but doesn&amp;#39;t jump out of the
loop if the bus is kept active by a client. This is not expected. A
malicious or buggy i2c client can hang the kernel in this case and
should be avoided. This is observed during a long time test with a
PCA953x GPIO extender.&lt;/p&gt;
&lt;p&gt;Fix it by changing the logic to not only sets the return value, but also
jumps out of the loop and return to the caller with -ETIMEDOUT.&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;i2c: qup: jump out of the loop in case of timeout&lt;/p&gt;
&lt;p&gt;Original logic only sets the return value but doesn&amp;#39;t jump out of the
loop if the bus is kept active by a client. This is not expected. A
malicious or buggy i2c client can hang the kernel in this case and
should be avoided. This is observed during a long time test with a
PCA953x GPIO extender.&lt;/p&gt;
&lt;p&gt;Fix it by changing the logic to not only sets the return value, but also
jumps out of the loop and return to the caller with -ETIMEDOUT.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38671</guid>
    </item>
    <item>
      <title>GHSA-hmc7-frwx-fp3p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hmc7-frwx-fp3p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i2c: qup: jump out of the loop in case of timeout&lt;/p&gt;
&lt;p&gt;Original logic only sets the return value but doesn&amp;#39;t jump out of the
loop if the bus is kept active by a client. This is not expected. A
malicious or buggy i2c client can hang the kernel in this case and
should be avoided. This is observed during a long time test with a
PCA953x GPIO extender.&lt;/p&gt;
&lt;p&gt;Fix it by changing the logic to not only sets the return value, but also
jumps out of the loop and return to the caller with -ETIMEDOUT.&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;i2c: qup: jump out of the loop in case of timeout&lt;/p&gt;
&lt;p&gt;Original logic only sets the return value but doesn&amp;#39;t jump out of the
loop if the bus is kept active by a client. This is not expected. A
malicious or buggy i2c client can hang the kernel in this case and
should be avoided. This is observed during a long time test with a
PCA953x GPIO extender.&lt;/p&gt;
&lt;p&gt;Fix it by changing the logic to not only sets the return value, but also
jumps out of the loop and return to the caller with -ETIMEDOUT.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hmc7-frwx-fp3p</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38671 — i2c: qup: jump out of the loop in case of timeout</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38671</link>
      <description>msrc_CVE-2025-38671</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38671</guid>
    </item>
    <item>
      <title>OESA-2025-2118 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2118</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;netfilter: nf_tables: avoid skb access on nf_stolen&lt;/p&gt;
&lt;p&gt;When verdict is NF_STOLEN, the skb might have been freed.&lt;/p&gt;
&lt;p&gt;When tracing is enabled, this can result in a use-after-free:
1. access to skb-&amp;amp;gt;nf_trace
2. access to skb-&amp;amp;gt;mark
3. computation of trace id
4. dump of packet payload&lt;/p&gt;
&lt;p&gt;To avoid 1, keep a cached copy of skb-&amp;amp;gt;nf_trace in the
trace state struct.
Refresh this copy whenever verdict is != STOLEN.&lt;/p&gt;
&lt;p&gt;Avoid 2 by skipping skb-&amp;amp;gt;mark access if verdict is STOLEN.&lt;/p&gt;
&lt;p&gt;3 is avoided by precomputing the trace id.&lt;/p&gt;
&lt;p&gt;Only dump the packet when verdict is not &amp;amp;quot;STOLEN&amp;amp;quot;.(CVE-2022-49622)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: release svc_expkey/svc_export with rcu_work&lt;/p&gt;
&lt;p&gt;The last reference for `cache_head` can be reduced to zero in `c_show`
and `e_show`(using `rcu_read_lock` and `rcu_read_unlock`). Consequently,
`svc_export_put` and `expkey_put` will be invoked, leading to two
issues:&lt;/p&gt;
&lt;p&gt;1. The `svc_export_put` will directly free ex_uuid. However,
   `e_show`/`c_show` will access `ex_uuid` after `cache_put`, which can
   trigger a use-after-free issue, shown below.&lt;/p&gt;
&lt;p&gt;==================================================================
   BUG: KASAN: slab-use-after-free in svc_export_show+0x362/0x430 [nfsd]
   Read of size 1 at addr ff11000010fdc120 by task cat/870&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 870 Comm: cat…&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;netfilter: nf_tables: avoid skb access on nf_stolen&lt;/p&gt;
&lt;p&gt;When verdict is NF_STOLEN, the skb might have been freed.&lt;/p&gt;
&lt;p&gt;When tracing is enabled, this can result in a use-after-free:
1. access to skb-&amp;amp;gt;nf_trace
2. access to skb-&amp;amp;gt;mark
3. computation of trace id
4. dump of packet payload&lt;/p&gt;
&lt;p&gt;To avoid 1, keep a cached copy of skb-&amp;amp;gt;nf_trace in the
trace state struct.
Refresh this copy whenever verdict is != STOLEN.&lt;/p&gt;
&lt;p&gt;Avoid 2 by skipping skb-&amp;amp;gt;mark access if verdict is STOLEN.&lt;/p&gt;
&lt;p&gt;3 is avoided by precomputing the trace id.&lt;/p&gt;
&lt;p&gt;Only dump the packet when verdict is not &amp;amp;quot;STOLEN&amp;amp;quot;.(CVE-2022-49622)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: release svc_expkey/svc_export with rcu_work&lt;/p&gt;
&lt;p&gt;The last reference for `cache_head` can be reduced to zero in `c_show`
and `e_show`(using `rcu_read_lock` and `rcu_read_unlock`). Consequently,
`svc_export_put` and `expkey_put` will be invoked, leading to two
issues:&lt;/p&gt;
&lt;p&gt;1. The `svc_export_put` will directly free ex_uuid. However,
   `e_show`/`c_show` will access `ex_uuid` after `cache_put`, which can
   trigger a use-after-free issue, shown below.&lt;/p&gt;
&lt;p&gt;==================================================================
   BUG: KASAN: slab-use-after-free in svc_export_show+0x362/0x430 [nfsd]
   Read of size 1 at addr ff11000010fdc120 by task cat/870&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 870 Comm: cat…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2118</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-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/opensuse-su-2025:20081-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03272-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:03272-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:03272-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38671</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38671</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 187 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: i2c: qup: jump out of the loop in case of timeout Original logic only sets the return value but doesn&amp;#39;t jump out of the loop if the bus is kept active by a client. This is not expected. A malicious or buggy i2c client can hang the kernel in this case and should be avoided. This is observed during a long time test with a PCA953x GPIO extender. Fix it by changing the logic to not only sets the return value, but also jumps out of the loop and return to the caller with -ETIMEDOUT.&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 187 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: i2c: qup: jump out of the loop in case of timeout Original logic only sets the return value but doesn&amp;#39;t jump out of the loop if the bus is kept active by a client. This is not expected. A malicious or buggy i2c client can hang the kernel in this case and should be avoided. This is observed during a long time test with a PCA953x GPIO extender. Fix it by changing the logic to not only sets the return value, but also jumps out of the loop and return to the caller with -ETIMEDOUT.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38671</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1898 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und Privilegieneskalation</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898</guid>
    </item>
  </channel>
</rss>
