<?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 02:18:31 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-03466</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03466</link>
      <description>bdu:2025-03466</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03466</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0693 — 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-2024-avi-0693</link>
      <description>certfr-2024-avi-0693</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0693</guid>
    </item>
    <item>
      <title>EUVD-2026-344592</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344592</link>
      <description>EUVD-2026-344592</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344592</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48816</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48816</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;SUNRPC: lock against -&amp;gt;sock changing during sysfs read&lt;/p&gt;
&lt;p&gt;-&amp;gt;sock can be set to NULL asynchronously unless -&amp;gt;recv_mutex is held.
So it is important to hold that mutex.  Otherwise a sysfs read can
trigger an oops.
Commit 17f09d3f619a (&amp;#34;SUNRPC: Check if the xprt is connected before
handling sysfs reads&amp;#34;) appears to attempt to fix this problem, but it
only narrows the race window.&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;SUNRPC: lock against -&amp;gt;sock changing during sysfs read&lt;/p&gt;
&lt;p&gt;-&amp;gt;sock can be set to NULL asynchronously unless -&amp;gt;recv_mutex is held.
So it is important to hold that mutex.  Otherwise a sysfs read can
trigger an oops.
Commit 17f09d3f619a (&amp;#34;SUNRPC: Check if the xprt is connected before
handling sysfs reads&amp;#34;) appears to attempt to fix this problem, but it
only narrows the race window.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48816</guid>
    </item>
    <item>
      <title>GHSA-9wm5-v97c-mv82</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9wm5-v97c-mv82</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;SUNRPC: lock against -&amp;gt;sock changing during sysfs read&lt;/p&gt;
&lt;p&gt;-&amp;gt;sock can be set to NULL asynchronously unless -&amp;gt;recv_mutex is held.
So it is important to hold that mutex.  Otherwise a sysfs read can
trigger an oops.
Commit 17f09d3f619a (&amp;#34;SUNRPC: Check if the xprt is connected before
handling sysfs reads&amp;#34;) appears to attempt to fix this problem, but it
only narrows the race window.&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;SUNRPC: lock against -&amp;gt;sock changing during sysfs read&lt;/p&gt;
&lt;p&gt;-&amp;gt;sock can be set to NULL asynchronously unless -&amp;gt;recv_mutex is held.
So it is important to hold that mutex.  Otherwise a sysfs read can
trigger an oops.
Commit 17f09d3f619a (&amp;#34;SUNRPC: Check if the xprt is connected before
handling sysfs reads&amp;#34;) appears to attempt to fix this problem, but it
only narrows the race window.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9wm5-v97c-mv82</guid>
    </item>
    <item>
      <title>msrc_CVE-2022-48816 — SUNRPC: lock against -&gt;sock changing during sysfs read</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2022-48816</link>
      <description>msrc_CVE-2022-48816</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2022-48816</guid>
    </item>
    <item>
      <title>OESA-2024-1894 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1894</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
lib/generic-radix-tree.c: Don&amp;amp;apos;t overflow in peek()&#13;
&#13;
When we started spreading new inode numbers throughout most of the 64
bit inode space, that triggered some corner case bugs, in particular
some integer overflows related to the radix tree code. Oops.(CVE-2021-47432)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
scsi: ufs: Fix a deadlock in the error handler&#13;
&#13;
The following deadlock has been observed on a test setup:&#13;
&#13;
 - All tags allocated&#13;
&#13;
 - The SCSI error handler calls ufshcd_eh_host_reset_handler()&#13;
&#13;
 - ufshcd_eh_host_reset_handler() queues work that calls
   ufshcd_err_handler()&#13;
&#13;
 - ufshcd_err_handler() locks up as follows:&#13;
&#13;
Workqueue: ufs_eh_wq_0 ufshcd_err_handler.cfi_jt
Call trace:
 __switch_to+0x298/0x5d8
 __schedule+0x6cc/0xa94
 schedule+0x12c/0x298
 blk_mq_get_tag+0x210/0x480
 __blk_mq_alloc_request+0x1c8/0x284
 blk_get_request+0x74/0x134
 ufshcd_exec_dev_cmd+0x68/0x640
 ufshcd_verify_dev_init+0x68/0x35c
 ufshcd_probe_hba+0x12c/0x1cb8
 ufshcd_host_reset_and_restore+0x88/0x254
 ufshcd_reset_and_restore+0xd0/0x354
 ufshcd_err_handler+0x408/0xc58
 process_one_work+0x24c/0x66c
 worker_thread+0x3e8/0xa4c
 kthread+0x150/0x1b4
 ret_from_fork+0x10/0x30&#13;
&#13;
Fix this lockup by making ufshcd_exec_dev_cmd() allocate a reserved
request.(CVE-2021-47622)&#13;
&#13;
In the Linux kernel, the following…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
lib/generic-radix-tree.c: Don&amp;amp;apos;t overflow in peek()&#13;
&#13;
When we started spreading new inode numbers throughout most of the 64
bit inode space, that triggered some corner case bugs, in particular
some integer overflows related to the radix tree code. Oops.(CVE-2021-47432)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
scsi: ufs: Fix a deadlock in the error handler&#13;
&#13;
The following deadlock has been observed on a test setup:&#13;
&#13;
 - All tags allocated&#13;
&#13;
 - The SCSI error handler calls ufshcd_eh_host_reset_handler()&#13;
&#13;
 - ufshcd_eh_host_reset_handler() queues work that calls
   ufshcd_err_handler()&#13;
&#13;
 - ufshcd_err_handler() locks up as follows:&#13;
&#13;
Workqueue: ufs_eh_wq_0 ufshcd_err_handler.cfi_jt
Call trace:
 __switch_to+0x298/0x5d8
 __schedule+0x6cc/0xa94
 schedule+0x12c/0x298
 blk_mq_get_tag+0x210/0x480
 __blk_mq_alloc_request+0x1c8/0x284
 blk_get_request+0x74/0x134
 ufshcd_exec_dev_cmd+0x68/0x640
 ufshcd_verify_dev_init+0x68/0x35c
 ufshcd_probe_hba+0x12c/0x1cb8
 ufshcd_host_reset_and_restore+0x88/0x254
 ufshcd_reset_and_restore+0xd0/0x354
 ufshcd_err_handler+0x408/0xc58
 process_one_work+0x24c/0x66c
 worker_thread+0x3e8/0xa4c
 kthread+0x150/0x1b4
 ret_from_fork+0x10/0x30&#13;
&#13;
Fix this lockup by making ufshcd_exec_dev_cmd() allocate a reserved
request.(CVE-2021-47622)&#13;
&#13;
In the Linux kernel, the following…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1894</guid>
    </item>
    <item>
      <title>RHSA-2024:6990 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:6990</link>
      <description>&lt;p&gt;kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: net/smc: Fix NULL pointer dereferencing in smc_vlan_by_tcpsk() kernel: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create kernel: vsock: remove vsock from connected table when connect is interrupted by a signal kernel: perf: Fix list corruption in perf_cgroup_switch() kernel: SUNRPC: lock against -&amp;amp;gt;sock changing during sysfs read kernel: mm/sparsemem: fix race in accessing memory_section-&amp;gt;usage kernel: ACPICA: Revert &amp;amp;#34;ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine.&amp;amp;#34; kernel: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() kernel: mm: prevent derefencing NULL ptr in pfn_section_valid() kernel: wifi: mac80211: Avoid address calculations via out of bounds array indexing&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: net/smc: Fix NULL pointer dereferencing in smc_vlan_by_tcpsk() kernel: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create kernel: vsock: remove vsock from connected table when connect is interrupted by a signal kernel: perf: Fix list corruption in perf_cgroup_switch() kernel: SUNRPC: lock against -&amp;amp;gt;sock changing during sysfs read kernel: mm/sparsemem: fix race in accessing memory_section-&amp;gt;usage kernel: ACPICA: Revert &amp;amp;#34;ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine.&amp;amp;#34; kernel: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() kernel: mm: prevent derefencing NULL ptr in pfn_section_valid() kernel: wifi: mac80211: Avoid address calculations via out of bounds array indexing&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:6990</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2894-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2894-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:2894-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48816</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48816</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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 99 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: SUNRPC: lock against -&amp;gt;sock changing during sysfs read -&amp;gt;sock can be set to NULL asynchronously unless -&amp;gt;recv_mutex is held. So it is important to hold that mutex.  Otherwise a sysfs read can trigger an oops. Commit 17f09d3f619a (&amp;#34;SUNRPC: Check if the xprt is connected before handling sysfs reads&amp;#34;) appears to attempt to fix this problem, but it only narrows the race window.&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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 99 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: SUNRPC: lock against -&amp;gt;sock changing during sysfs read -&amp;gt;sock can be set to NULL asynchronously unless -&amp;gt;recv_mutex is held. So it is important to hold that mutex.  Otherwise a sysfs read can trigger an oops. Commit 17f09d3f619a (&amp;#34;SUNRPC: Check if the xprt is connected before handling sysfs reads&amp;#34;) appears to attempt to fix this problem, but it only narrows the race window.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48816</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1625 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1625</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen 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-1625</guid>
    </item>
  </channel>
</rss>
