<?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 12:47:56 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-14600</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-14600</link>
      <description>bdu:2025-14600</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-14600</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0496 — 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-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>EUVD-2026-309736</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309736</link>
      <description>EUVD-2026-309736</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309736</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47430</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47430</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n&lt;/p&gt;
&lt;p&gt;Commit&lt;/p&gt;
&lt;p&gt;3c73b81a9164 (&amp;#34;x86/entry, selftests: Further improve user entry sanity checks&amp;#34;)&lt;/p&gt;
&lt;p&gt;added a warning if AC is set when in the kernel.&lt;/p&gt;
&lt;p&gt;Commit&lt;/p&gt;
&lt;p&gt;662a0221893a3d (&amp;#34;x86/entry: Fix AC assertion&amp;#34;)&lt;/p&gt;
&lt;p&gt;changed the warning to only fire if the CPU supports SMAP.&lt;/p&gt;
&lt;p&gt;However, the warning can still trigger on a machine that supports SMAP
but where it&amp;#39;s disabled in the kernel config and when running the
syscall_nt selftest, for example:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  WARNING: CPU: 0 PID: 49 at irqentry_enter_from_user_mode
  CPU: 0 PID: 49 Comm: init Tainted: G                T 5.15.0-rc4+ #98 e6202628ee053b4f310759978284bd8bb0ce6905
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014
  RIP: 0010:irqentry_enter_from_user_mode
  ...
  Call Trace:
   ? irqentry_enter
   ? exc_general_protection
   ? asm_exc_general_protection
   ? asm_exc_general_protectio&lt;/p&gt;
&lt;p&gt;IS_ENABLED(CONFIG_X86_SMAP) could be added to the warning condition, but
even this would not be enough in case SMAP is disabled at boot time with
the &amp;#34;nosmap&amp;#34; parameter.&lt;/p&gt;
&lt;p&gt;To be consistent with &amp;#34;nosmap&amp;#34; behaviour, clear X86_FEATURE_SMAP when
!CONFIG_X86_SMAP.&lt;/p&gt;
&lt;p&gt;Found using entry-fuzz + satrandconfig.&lt;/p&gt;
&lt;p&gt;[ bp: Massage commit message. ]&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;x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n&lt;/p&gt;
&lt;p&gt;Commit&lt;/p&gt;
&lt;p&gt;3c73b81a9164 (&amp;#34;x86/entry, selftests: Further improve user entry sanity checks&amp;#34;)&lt;/p&gt;
&lt;p&gt;added a warning if AC is set when in the kernel.&lt;/p&gt;
&lt;p&gt;Commit&lt;/p&gt;
&lt;p&gt;662a0221893a3d (&amp;#34;x86/entry: Fix AC assertion&amp;#34;)&lt;/p&gt;
&lt;p&gt;changed the warning to only fire if the CPU supports SMAP.&lt;/p&gt;
&lt;p&gt;However, the warning can still trigger on a machine that supports SMAP
but where it&amp;#39;s disabled in the kernel config and when running the
syscall_nt selftest, for example:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  WARNING: CPU: 0 PID: 49 at irqentry_enter_from_user_mode
  CPU: 0 PID: 49 Comm: init Tainted: G                T 5.15.0-rc4+ #98 e6202628ee053b4f310759978284bd8bb0ce6905
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014
  RIP: 0010:irqentry_enter_from_user_mode
  ...
  Call Trace:
   ? irqentry_enter
   ? exc_general_protection
   ? asm_exc_general_protection
   ? asm_exc_general_protectio&lt;/p&gt;
&lt;p&gt;IS_ENABLED(CONFIG_X86_SMAP) could be added to the warning condition, but
even this would not be enough in case SMAP is disabled at boot time with
the &amp;#34;nosmap&amp;#34; parameter.&lt;/p&gt;
&lt;p&gt;To be consistent with &amp;#34;nosmap&amp;#34; behaviour, clear X86_FEATURE_SMAP when
!CONFIG_X86_SMAP.&lt;/p&gt;
&lt;p&gt;Found using entry-fuzz + satrandconfig.&lt;/p&gt;
&lt;p&gt;[ bp: Massage commit message. ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47430</guid>
    </item>
    <item>
      <title>GHSA-7wxc-v995-9mmf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7wxc-v995-9mmf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n&lt;/p&gt;
&lt;p&gt;Commit&lt;/p&gt;
&lt;p&gt;3c73b81a9164 (&amp;#34;x86/entry, selftests: Further improve user entry sanity checks&amp;#34;)&lt;/p&gt;
&lt;p&gt;added a warning if AC is set when in the kernel.&lt;/p&gt;
&lt;p&gt;Commit&lt;/p&gt;
&lt;p&gt;662a0221893a3d (&amp;#34;x86/entry: Fix AC assertion&amp;#34;)&lt;/p&gt;
&lt;p&gt;changed the warning to only fire if the CPU supports SMAP.&lt;/p&gt;
&lt;p&gt;However, the warning can still trigger on a machine that supports SMAP
but where it&amp;#39;s disabled in the kernel config and when running the
syscall_nt selftest, for example:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  WARNING: CPU: 0 PID: 49 at irqentry_enter_from_user_mode
  CPU: 0 PID: 49 Comm: init Tainted: G                T 5.15.0-rc4+ #98 e6202628ee053b4f310759978284bd8bb0ce6905
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014
  RIP: 0010:irqentry_enter_from_user_mode
  ...
  Call Trace:
   ? irqentry_enter
   ? exc_general_protection
   ? asm_exc_general_protection
   ? asm_exc_general_protectio&lt;/p&gt;
&lt;p&gt;IS_ENABLED(CONFIG_X86_SMAP) could be added to the warning condition, but
even this would not be enough in case SMAP is disabled at boot time with
the &amp;#34;nosmap&amp;#34; parameter.&lt;/p&gt;
&lt;p&gt;To be consistent with &amp;#34;nosmap&amp;#34; behaviour, clear X86_FEATURE_SMAP when
!CONFIG_X86_SMAP.&lt;/p&gt;
&lt;p&gt;Found using entry-fuzz + satrandconfig.&lt;/p&gt;
&lt;p&gt;[ bp: Massage commit message. ]&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;x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n&lt;/p&gt;
&lt;p&gt;Commit&lt;/p&gt;
&lt;p&gt;3c73b81a9164 (&amp;#34;x86/entry, selftests: Further improve user entry sanity checks&amp;#34;)&lt;/p&gt;
&lt;p&gt;added a warning if AC is set when in the kernel.&lt;/p&gt;
&lt;p&gt;Commit&lt;/p&gt;
&lt;p&gt;662a0221893a3d (&amp;#34;x86/entry: Fix AC assertion&amp;#34;)&lt;/p&gt;
&lt;p&gt;changed the warning to only fire if the CPU supports SMAP.&lt;/p&gt;
&lt;p&gt;However, the warning can still trigger on a machine that supports SMAP
but where it&amp;#39;s disabled in the kernel config and when running the
syscall_nt selftest, for example:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  WARNING: CPU: 0 PID: 49 at irqentry_enter_from_user_mode
  CPU: 0 PID: 49 Comm: init Tainted: G                T 5.15.0-rc4+ #98 e6202628ee053b4f310759978284bd8bb0ce6905
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014
  RIP: 0010:irqentry_enter_from_user_mode
  ...
  Call Trace:
   ? irqentry_enter
   ? exc_general_protection
   ? asm_exc_general_protection
   ? asm_exc_general_protectio&lt;/p&gt;
&lt;p&gt;IS_ENABLED(CONFIG_X86_SMAP) could be added to the warning condition, but
even this would not be enough in case SMAP is disabled at boot time with
the &amp;#34;nosmap&amp;#34; parameter.&lt;/p&gt;
&lt;p&gt;To be consistent with &amp;#34;nosmap&amp;#34; behaviour, clear X86_FEATURE_SMAP when
!CONFIG_X86_SMAP.&lt;/p&gt;
&lt;p&gt;Found using entry-fuzz + satrandconfig.&lt;/p&gt;
&lt;p&gt;[ bp: Massage commit message. ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7wxc-v995-9mmf</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2008-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2008-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:2008-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47430</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47430</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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n Commit   3c73b81a9164 (&amp;#34;x86/entry, selftests: Further improve user entry sanity checks&amp;#34;) added a warning if AC is set when in the kernel. Commit   662a0221893a3d (&amp;#34;x86/entry: Fix AC assertion&amp;#34;) changed the warning to only fire if the CPU supports SMAP. However, the warning can still trigger on a machine that supports SMAP but where it&amp;#39;s disabled in the kernel config and when running the syscall_nt selftest, for example:   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 49 at irqentry_enter_from_user_mode   CPU: 0 PID: 49 Comm: init Tainted: G                T 5.15.0-rc4+ #98 e6202628ee053b4f310759978284bd8bb0ce6905   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014   RIP: 0010:irqentry_enter_from_user_mode   ...   Call Trace:    ? irqentry_enter    ? exc_general_protection    ? asm_exc_general_protection    ? asm_exc_general_protectio IS_ENABLED(CONFIG_X86_SMAP) could be added to the warning condition, but even this would not be enough in case SMAP is disabled at boot time with the &amp;#34;nosmap&amp;#34; parameter. To be consistent with &amp;#34;nosmap&amp;#34; behaviour, clear X86_FEATURE_SMAP when !CONFIG_X86_SMAP. Found using entry-fuzz + satrandconfig.  [ bp: Massage commit message. ]&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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n Commit   3c73b81a9164 (&amp;#34;x86/entry, selftests: Further improve user entry sanity checks&amp;#34;) added a warning if AC is set when in the kernel. Commit   662a0221893a3d (&amp;#34;x86/entry: Fix AC assertion&amp;#34;) changed the warning to only fire if the CPU supports SMAP. However, the warning can still trigger on a machine that supports SMAP but where it&amp;#39;s disabled in the kernel config and when running the syscall_nt selftest, for example:   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 49 at irqentry_enter_from_user_mode   CPU: 0 PID: 49 Comm: init Tainted: G                T 5.15.0-rc4+ #98 e6202628ee053b4f310759978284bd8bb0ce6905   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014   RIP: 0010:irqentry_enter_from_user_mode   ...   Call Trace:    ? irqentry_enter    ? exc_general_protection    ? asm_exc_general_protection    ? asm_exc_general_protectio IS_ENABLED(CONFIG_X86_SMAP) could be added to the warning condition, but even this would not be enough in case SMAP is disabled at boot time with the &amp;#34;nosmap&amp;#34; parameter. To be consistent with &amp;#34;nosmap&amp;#34; behaviour, clear X86_FEATURE_SMAP when !CONFIG_X86_SMAP. Found using entry-fuzz + satrandconfig.  [ bp: Massage commit message. ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47430</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1197 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1197</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1197</guid>
    </item>
  </channel>
</rss>
