<?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 17:48:53 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06527</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06527</link>
      <description>bdu:2024-06527</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06527</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-310152</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310152</link>
      <description>EUVD-2026-310152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310152</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48793</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48793</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: x86: nSVM: fix potential NULL derefernce on nested migration&lt;/p&gt;
&lt;p&gt;Turns out that due to review feedback and/or rebases
I accidentally moved the call to nested_svm_load_cr3 to be too early,
before the NPT is enabled, which is very wrong to do.&lt;/p&gt;
&lt;p&gt;KVM can&amp;#39;t even access guest memory at that point as nested NPT
is needed for that, and of course it won&amp;#39;t initialize the walk_mmu,
which is main issue the patch was addressing.&lt;/p&gt;
&lt;p&gt;Fix this for real.&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: x86: nSVM: fix potential NULL derefernce on nested migration&lt;/p&gt;
&lt;p&gt;Turns out that due to review feedback and/or rebases
I accidentally moved the call to nested_svm_load_cr3 to be too early,
before the NPT is enabled, which is very wrong to do.&lt;/p&gt;
&lt;p&gt;KVM can&amp;#39;t even access guest memory at that point as nested NPT
is needed for that, and of course it won&amp;#39;t initialize the walk_mmu,
which is main issue the patch was addressing.&lt;/p&gt;
&lt;p&gt;Fix this for real.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48793</guid>
    </item>
    <item>
      <title>GHSA-p5hp-9793-2w9c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p5hp-9793-2w9c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: x86: nSVM: fix potential NULL derefernce on nested migration&lt;/p&gt;
&lt;p&gt;Turns out that due to review feedback and/or rebases
I accidentally moved the call to nested_svm_load_cr3 to be too early,
before the NPT is enabled, which is very wrong to do.&lt;/p&gt;
&lt;p&gt;KVM can&amp;#39;t even access guest memory at that point as nested NPT
is needed for that, and of course it won&amp;#39;t initialize the walk_mmu,
which is main issue the patch was addressing.&lt;/p&gt;
&lt;p&gt;Fix this for real.&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: x86: nSVM: fix potential NULL derefernce on nested migration&lt;/p&gt;
&lt;p&gt;Turns out that due to review feedback and/or rebases
I accidentally moved the call to nested_svm_load_cr3 to be too early,
before the NPT is enabled, which is very wrong to do.&lt;/p&gt;
&lt;p&gt;KVM can&amp;#39;t even access guest memory at that point as nested NPT
is needed for that, and of course it won&amp;#39;t initialize the walk_mmu,
which is main issue the patch was addressing.&lt;/p&gt;
&lt;p&gt;Fix this for real.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p5hp-9793-2w9c</guid>
    </item>
    <item>
      <title>RHSA-2024:5692 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:5692</link>
      <description>&lt;p&gt;kernel: ipc/mqueue, msg, sem: avoid relying on a stack reference past its expiry kernel: mISDN: fix possible use-after-free in HFC_cleanup() kernel: isdn: mISDN: Fix sleeping function called from invalid context kernel: KVM: x86: nSVM: fix potential NULL derefernce on nested migration kernel: perf: Fix list corruption in perf_cgroup_switch() kernel: smb: client: fix potential OOBs in smb2_parse_contexts() kernel: net/sched: act_ct: fix skb leak and crash on ooo frags kernel: platform/x86: wmi: Fix opening of char device kernel: wifi: iwlwifi: dbg-tlv: ensure NUL termination kernel: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() kernel: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). kernel: wifi: nl80211: don&amp;amp;#39;t free NULL coalescing rule kernel: gfs2: Fix potential glock use-after-free on unmount&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: ipc/mqueue, msg, sem: avoid relying on a stack reference past its expiry kernel: mISDN: fix possible use-after-free in HFC_cleanup() kernel: isdn: mISDN: Fix sleeping function called from invalid context kernel: KVM: x86: nSVM: fix potential NULL derefernce on nested migration kernel: perf: Fix list corruption in perf_cgroup_switch() kernel: smb: client: fix potential OOBs in smb2_parse_contexts() kernel: net/sched: act_ct: fix skb leak and crash on ooo frags kernel: platform/x86: wmi: Fix opening of char device kernel: wifi: iwlwifi: dbg-tlv: ensure NUL termination kernel: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() kernel: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). kernel: wifi: nl80211: don&amp;amp;#39;t free NULL coalescing rule kernel: gfs2: Fix potential glock use-after-free on unmount&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:5692</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-48793</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48793</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 61 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: nSVM: fix potential NULL derefernce on nested migration Turns out that due to review feedback and/or rebases I accidentally moved the call to nested_svm_load_cr3 to be too early, before the NPT is enabled, which is very wrong to do. KVM can&amp;#39;t even access guest memory at that point as nested NPT is needed for that, and of course it won&amp;#39;t initialize the walk_mmu, which is main issue the patch was addressing. Fix this for real.&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 61 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: nSVM: fix potential NULL derefernce on nested migration Turns out that due to review feedback and/or rebases I accidentally moved the call to nested_svm_load_cr3 to be too early, before the NPT is enabled, which is very wrong to do. KVM can&amp;#39;t even access guest memory at that point as nested NPT is needed for that, and of course it won&amp;#39;t initialize the walk_mmu, which is main issue the patch was addressing. Fix this for real.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48793</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>
