<?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 08:45:37 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-00153</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-00153</link>
      <description>bdu:2023-00153</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-00153</guid>
    </item>
    <item>
      <title>certfr-2022-avi-1083 — De multiples vulnérabilités ont été découvertes dans Xen. Elles
permettent à un attaquant de provoquer un déni de servi…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2022-avi-1083</link>
      <description>certfr-2022-avi-1083</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2022-avi-1083</guid>
    </item>
    <item>
      <title>EUVD-2026-233002</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233002</link>
      <description>EUVD-2026-233002</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233002</guid>
    </item>
    <item>
      <title>fkie_cve-2022-42329</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-42329</link>
      <description>&lt;p&gt;Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock could occur in case of netpoll being active for the interface the xen-netback driver is connected to (CVE-2022-42329).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock could occur in case of netpoll being active for the interface the xen-netback driver is connected to (CVE-2022-42329).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-42329</guid>
    </item>
    <item>
      <title>GHSA-ghhc-93hq-6rqv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ghhc-93hq-6rqv</link>
      <description>&lt;p&gt;Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock could occur in case of netpoll being active for the interface the xen-netback driver is connected to (CVE-2022-42329).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock could occur in case of netpoll being active for the interface the xen-netback driver is connected to (CVE-2022-42329).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ghhc-93hq-6rqv</guid>
    </item>
    <item>
      <title>gsd-2022-42329</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-42329</link>
      <description>gsd-2022-42329</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-42329</guid>
    </item>
    <item>
      <title>ICSA-23-166-11 — Siemens SIMATIC S7-1500 TM MFP Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-23-166-11</link>
      <description>&lt;p&gt;json-c through 0.14 has an integer overflow and out-of-bounds write via a large JSON file, as demonstrated by printbuf_memappend. A memory overflow vulnerability was found in the Linux kernel’s ipc functionality of the memcg subsystem, in the way a user calls the semget function multiple times, creating semaphores. This flaw allows a local user to starve the resources, causing a denial of service. The highest threat from this vulnerability is to system availability. A vulnerability was found in the fs/inode.c:inode_init_owner() function logic of the LInux kernel that allows local users to create files for the XFS file-system with an unintended group ownership and with group execution and SGID permission bits set, in a scenario where a directory is SGID and belongs to a certain group and is writable by a user who is not a member of this group. This can lead to excessive permissions granted in case when they should not. This vulnerability is similar to the previous CVE-2018-13405 and adds the missed fix for the XFS. When sending malicous data to kernel by ioctl cmd FBIOPUT_VSCREENINFO,kernel will write memory out of bounds. In gc_data_segment in fs/f2fs/gc.c in the Linux kernel before 5.16.3, special files are not considered, leading to a move_data_page NULL pointer dereference. A flaw was found in the Linux kernel. The existing KVM SEV API has a vulnerability that allows a non-root (host) user-level application to crash the host kernel by creating a confidential guest VM inst…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;json-c through 0.14 has an integer overflow and out-of-bounds write via a large JSON file, as demonstrated by printbuf_memappend. A memory overflow vulnerability was found in the Linux kernel’s ipc functionality of the memcg subsystem, in the way a user calls the semget function multiple times, creating semaphores. This flaw allows a local user to starve the resources, causing a denial of service. The highest threat from this vulnerability is to system availability. A vulnerability was found in the fs/inode.c:inode_init_owner() function logic of the LInux kernel that allows local users to create files for the XFS file-system with an unintended group ownership and with group execution and SGID permission bits set, in a scenario where a directory is SGID and belongs to a certain group and is writable by a user who is not a member of this group. This can lead to excessive permissions granted in case when they should not. This vulnerability is similar to the previous CVE-2018-13405 and adds the missed fix for the XFS. When sending malicous data to kernel by ioctl cmd FBIOPUT_VSCREENINFO,kernel will write memory out of bounds. In gc_data_segment in fs/f2fs/gc.c in the Linux kernel before 5.16.3, special files are not considered, leading to a move_data_page NULL pointer dereference. A flaw was found in the Linux kernel. The existing KVM SEV API has a vulnerability that allows a non-root (host) user-level application to crash the host kernel by creating a confidential guest VM inst…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-23-166-11</guid>
    </item>
    <item>
      <title>msrc_CVE-2022-42329 — Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs; the text exp…</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2022-42329</link>
      <description>msrc_CVE-2022-42329</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2022-42329</guid>
    </item>
    <item>
      <title>OESA-2022-2162 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2022-2162</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;Security Fix(es):&#13;
&#13;
A use-after-free flaw was found in Linux kernel before 5.19.2. This issue occurs in cmd_hdl_filter in drivers/staging/rtl8712/rtl8712_cmd.c, allowing an attacker to launch a local denial of service attack and gain escalation of privileges.(CVE-2022-4095)&#13;
&#13;
There are null-ptr-deref vulnerabilities in drivers/net/slip of linux that allow attacker to
crash linux kernel by simulating slip network card from user-space of linux.&#13;
&#13;
------------------------------------------&#13;
&#13;
[Root cause]&#13;
&#13;
When a slip driver is detaching, the slip_close() will act to
cleanup necessary resources and sl-&amp;amp;gt;tty is set to NULL in
slip_close(). Meanwhile, the packet we transmit is blocked,
sl_tx_timeout() will be called. Although slip_close() and
sl_tx_timeout() use sl-&amp;amp;gt;lock to synchronize, we don`t judge
whether sl-&amp;amp;gt;tty equals to NULL in sl_tx_timeout() and the
null pointer dereference bug will happen.&#13;
&#13;
(Thread 1) | (Thread 2)
| slip_close()
| spin_lock_bh(&amp;amp;amp;sl-&amp;amp;gt;lock)
| ...
... | sl-&amp;amp;gt;tty = NULL //(1)
sl_tx_timeout() | spin_unlock_bh(&amp;amp;amp;sl-&amp;amp;gt;lock)
spin_lock(&amp;amp;amp;sl-&amp;amp;gt;lock); |
... | ...
tty_chars_in_buffer(sl-&amp;amp;gt;tty)|
if (tty-&amp;amp;gt;ops-&amp;amp;gt;..) //(2) |
... | synchronize_rcu()&#13;
&#13;
We set NULL to sl-&amp;amp;gt;tty in position (1) and dereference sl-&amp;amp;gt;tty
in position (2).&#13;
&#13;
------------------------------------------(CVE-2022-41858)&#13;
&#13;
A flaw was found in the Linux kernel&amp;amp;apos;s Layer 2 Tunneling Protocol (L2TP). A missing lock when clearing sk_user_data can lead to…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;Security Fix(es):&#13;
&#13;
A use-after-free flaw was found in Linux kernel before 5.19.2. This issue occurs in cmd_hdl_filter in drivers/staging/rtl8712/rtl8712_cmd.c, allowing an attacker to launch a local denial of service attack and gain escalation of privileges.(CVE-2022-4095)&#13;
&#13;
There are null-ptr-deref vulnerabilities in drivers/net/slip of linux that allow attacker to
crash linux kernel by simulating slip network card from user-space of linux.&#13;
&#13;
------------------------------------------&#13;
&#13;
[Root cause]&#13;
&#13;
When a slip driver is detaching, the slip_close() will act to
cleanup necessary resources and sl-&amp;amp;gt;tty is set to NULL in
slip_close(). Meanwhile, the packet we transmit is blocked,
sl_tx_timeout() will be called. Although slip_close() and
sl_tx_timeout() use sl-&amp;amp;gt;lock to synchronize, we don`t judge
whether sl-&amp;amp;gt;tty equals to NULL in sl_tx_timeout() and the
null pointer dereference bug will happen.&#13;
&#13;
(Thread 1) | (Thread 2)
| slip_close()
| spin_lock_bh(&amp;amp;amp;sl-&amp;amp;gt;lock)
| ...
... | sl-&amp;amp;gt;tty = NULL //(1)
sl_tx_timeout() | spin_unlock_bh(&amp;amp;amp;sl-&amp;amp;gt;lock)
spin_lock(&amp;amp;amp;sl-&amp;amp;gt;lock); |
... | ...
tty_chars_in_buffer(sl-&amp;amp;gt;tty)|
if (tty-&amp;amp;gt;ops-&amp;amp;gt;..) //(2) |
... | synchronize_rcu()&#13;
&#13;
We set NULL to sl-&amp;amp;gt;tty in position (1) and dereference sl-&amp;amp;gt;tty
in position (2).&#13;
&#13;
------------------------------------------(CVE-2022-41858)&#13;
&#13;
A flaw was found in the Linux kernel&amp;amp;apos;s Layer 2 Tunneling Protocol (L2TP). A missing lock when clearing sk_user_data can lead to…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2022-2162</guid>
    </item>
    <item>
      <title>SUSE-SU-2022:4505-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2022:4505-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-2022:4505-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-42329</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-42329</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 108 more&lt;/p&gt;
&lt;p&gt;Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock could occur in case of netpoll being active for the interface the xen-netback driver is connected to (CVE-2022-42329).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 108 more&lt;/p&gt;
&lt;p&gt;Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock could occur in case of netpoll being active for the interface the xen-netback driver is connected to (CVE-2022-42329).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-42329</guid>
    </item>
    <item>
      <title>WID-SEC-W-2022-2250 — Xen: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2022-2250</link>
      <description>&lt;p&gt;Ein  Angreifer kann mehrere Schwachstellen in Xen ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein  Angreifer kann mehrere Schwachstellen in Xen ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2022-2250</guid>
    </item>
  </channel>
</rss>
