<?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>Sun, 04 Oct 2026 00:04:53 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02582</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02582</link>
      <description>bdu:2026-02582</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02582</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0587 — 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-0587</link>
      <description>certfr-2025-avi-0587</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587</guid>
    </item>
    <item>
      <title>EUVD-2026-310955</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310955</link>
      <description>EUVD-2026-310955</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310955</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50012</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50012</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/64: Init jump labels before parse_early_param()&lt;/p&gt;
&lt;p&gt;On 64-bit, calling jump_label_init() in setup_feature_keys() is too
late because static keys may be used in subroutines of
parse_early_param() which is again subroutine of early_init_devtree().&lt;/p&gt;
&lt;p&gt;For example booting with &amp;#34;threadirqs&amp;#34;:&lt;/p&gt;
&lt;p&gt;static_key_enable_cpuslocked(): static key &amp;#39;0xc000000002953260&amp;#39; used before call to jump_label_init()
  WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xfc/0x120
  ...
  NIP static_key_enable_cpuslocked+0xfc/0x120
  LR  static_key_enable_cpuslocked+0xf8/0x120
  Call Trace:
    static_key_enable_cpuslocked+0xf8/0x120 (unreliable)
    static_key_enable+0x30/0x50
    setup_forced_irqthreads+0x28/0x40
    do_early_param+0xa0/0x108
    parse_args+0x290/0x4e0
    parse_early_options+0x48/0x5c
    parse_early_param+0x58/0x84
    early_init_devtree+0xd4/0x518
    early_setup+0xb4/0x214&lt;/p&gt;
&lt;p&gt;So call jump_label_init() just before parse_early_param() in
early_init_devtree().&lt;/p&gt;
&lt;p&gt;[mpe: Add call trace to change log and minor wording edits.]&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;powerpc/64: Init jump labels before parse_early_param()&lt;/p&gt;
&lt;p&gt;On 64-bit, calling jump_label_init() in setup_feature_keys() is too
late because static keys may be used in subroutines of
parse_early_param() which is again subroutine of early_init_devtree().&lt;/p&gt;
&lt;p&gt;For example booting with &amp;#34;threadirqs&amp;#34;:&lt;/p&gt;
&lt;p&gt;static_key_enable_cpuslocked(): static key &amp;#39;0xc000000002953260&amp;#39; used before call to jump_label_init()
  WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xfc/0x120
  ...
  NIP static_key_enable_cpuslocked+0xfc/0x120
  LR  static_key_enable_cpuslocked+0xf8/0x120
  Call Trace:
    static_key_enable_cpuslocked+0xf8/0x120 (unreliable)
    static_key_enable+0x30/0x50
    setup_forced_irqthreads+0x28/0x40
    do_early_param+0xa0/0x108
    parse_args+0x290/0x4e0
    parse_early_options+0x48/0x5c
    parse_early_param+0x58/0x84
    early_init_devtree+0xd4/0x518
    early_setup+0xb4/0x214&lt;/p&gt;
&lt;p&gt;So call jump_label_init() just before parse_early_param() in
early_init_devtree().&lt;/p&gt;
&lt;p&gt;[mpe: Add call trace to change log and minor wording edits.]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50012</guid>
    </item>
    <item>
      <title>GHSA-crf3-x3fx-qg24</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-crf3-x3fx-qg24</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/64: Init jump labels before parse_early_param()&lt;/p&gt;
&lt;p&gt;On 64-bit, calling jump_label_init() in setup_feature_keys() is too
late because static keys may be used in subroutines of
parse_early_param() which is again subroutine of early_init_devtree().&lt;/p&gt;
&lt;p&gt;For example booting with &amp;#34;threadirqs&amp;#34;:&lt;/p&gt;
&lt;p&gt;static_key_enable_cpuslocked(): static key &amp;#39;0xc000000002953260&amp;#39; used before call to jump_label_init()
  WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xfc/0x120
  ...
  NIP static_key_enable_cpuslocked+0xfc/0x120
  LR  static_key_enable_cpuslocked+0xf8/0x120
  Call Trace:
    static_key_enable_cpuslocked+0xf8/0x120 (unreliable)
    static_key_enable+0x30/0x50
    setup_forced_irqthreads+0x28/0x40
    do_early_param+0xa0/0x108
    parse_args+0x290/0x4e0
    parse_early_options+0x48/0x5c
    parse_early_param+0x58/0x84
    early_init_devtree+0xd4/0x518
    early_setup+0xb4/0x214&lt;/p&gt;
&lt;p&gt;So call jump_label_init() just before parse_early_param() in
early_init_devtree().&lt;/p&gt;
&lt;p&gt;[mpe: Add call trace to change log and minor wording edits.]&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;powerpc/64: Init jump labels before parse_early_param()&lt;/p&gt;
&lt;p&gt;On 64-bit, calling jump_label_init() in setup_feature_keys() is too
late because static keys may be used in subroutines of
parse_early_param() which is again subroutine of early_init_devtree().&lt;/p&gt;
&lt;p&gt;For example booting with &amp;#34;threadirqs&amp;#34;:&lt;/p&gt;
&lt;p&gt;static_key_enable_cpuslocked(): static key &amp;#39;0xc000000002953260&amp;#39; used before call to jump_label_init()
  WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xfc/0x120
  ...
  NIP static_key_enable_cpuslocked+0xfc/0x120
  LR  static_key_enable_cpuslocked+0xf8/0x120
  Call Trace:
    static_key_enable_cpuslocked+0xf8/0x120 (unreliable)
    static_key_enable+0x30/0x50
    setup_forced_irqthreads+0x28/0x40
    do_early_param+0xa0/0x108
    parse_args+0x290/0x4e0
    parse_early_options+0x48/0x5c
    parse_early_param+0x58/0x84
    early_init_devtree+0xd4/0x518
    early_setup+0xb4/0x214&lt;/p&gt;
&lt;p&gt;So call jump_label_init() just before parse_early_param() in
early_init_devtree().&lt;/p&gt;
&lt;p&gt;[mpe: Add call trace to change log and minor wording edits.]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-crf3-x3fx-qg24</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02264-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02264-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:02264-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50012</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50012</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux and 147 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/64: Init jump labels before parse_early_param() On 64-bit, calling jump_label_init() in setup_feature_keys() is too late because static keys may be used in subroutines of parse_early_param() which is again subroutine of early_init_devtree(). For example booting with &amp;#34;threadirqs&amp;#34;:   static_key_enable_cpuslocked(): static key &amp;#39;0xc000000002953260&amp;#39; used before call to jump_label_init()   WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xfc/0x120   ...   NIP static_key_enable_cpuslocked+0xfc/0x120   LR  static_key_enable_cpuslocked+0xf8/0x120   Call Trace:     static_key_enable_cpuslocked+0xf8/0x120 (unreliable)     static_key_enable+0x30/0x50     setup_forced_irqthreads+0x28/0x40     do_early_param+0xa0/0x108     parse_args+0x290/0x4e0     parse_early_options+0x48/0x5c     parse_early_param+0x58/0x84     early_init_devtree+0xd4/0x518     early_setup+0xb4/0x214 So call jump_label_init() just before parse_early_param() in early_init_devtree(). [mpe: Add call trace to change log and minor wording edits.]&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:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux and 147 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/64: Init jump labels before parse_early_param() On 64-bit, calling jump_label_init() in setup_feature_keys() is too late because static keys may be used in subroutines of parse_early_param() which is again subroutine of early_init_devtree(). For example booting with &amp;#34;threadirqs&amp;#34;:   static_key_enable_cpuslocked(): static key &amp;#39;0xc000000002953260&amp;#39; used before call to jump_label_init()   WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xfc/0x120   ...   NIP static_key_enable_cpuslocked+0xfc/0x120   LR  static_key_enable_cpuslocked+0xf8/0x120   Call Trace:     static_key_enable_cpuslocked+0xf8/0x120 (unreliable)     static_key_enable+0x30/0x50     setup_forced_irqthreads+0x28/0x40     do_early_param+0xa0/0x108     parse_args+0x290/0x4e0     parse_early_options+0x48/0x5c     parse_early_param+0x58/0x84     early_init_devtree+0xd4/0x518     early_setup+0xb4/0x214 So call jump_label_init() just before parse_early_param() in early_init_devtree(). [mpe: Add call trace to change log and minor wording edits.]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50012</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel 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-2025-1350</guid>
    </item>
  </channel>
</rss>
