<?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 09:43:31 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05778</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05778</link>
      <description>bdu:2026-05778</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05778</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0509 — 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-0509</link>
      <description>certfr-2025-avi-0509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</guid>
    </item>
    <item>
      <title>EUVD-2026-310886</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310886</link>
      <description>EUVD-2026-310886</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310886</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49888</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49888</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64: entry: avoid kprobe recursion&lt;/p&gt;
&lt;p&gt;The cortex_a76_erratum_1463225_debug_handler() function is called when
handling debug exceptions (and synchronous exceptions from BRK
instructions), and so is called when a probed function executes. If the
compiler does not inline cortex_a76_erratum_1463225_debug_handler(), it
can be probed.&lt;/p&gt;
&lt;p&gt;If cortex_a76_erratum_1463225_debug_handler() is probed, any debug
exception or software breakpoint exception will result in recursive
exceptions leading to a stack overflow. This can be triggered with the
ftrace multiple_probes selftest, and as per the example splat below.&lt;/p&gt;
&lt;p&gt;This is a regression caused by commit:&lt;/p&gt;
&lt;p&gt;6459b8469753e9fe (&amp;#34;arm64: entry: consolidate Cortex-A76 erratum 1463225 workaround&amp;#34;)&lt;/p&gt;
&lt;p&gt;... which removed the NOKPROBE_SYMBOL() annotation associated with the
function.&lt;/p&gt;
&lt;p&gt;My intent was that cortex_a76_erratum_1463225_debug_handler() would be
inlined into its caller, el1_dbg(), which is marked noinstr and cannot
be probed. Mark cortex_a76_erratum_1463225_debug_handler() as
__always_inline to ensure this.&lt;/p&gt;
&lt;p&gt;Example splat prior to this patch (with recursive entries elided):&lt;/p&gt;
&lt;p&gt;| # echo p cortex_a76_erratum_1463225_debug_handler &amp;gt; /sys/kernel/debug/tracing/kprobe_events
| # echo p do_el0_svc &amp;gt;&amp;gt; /sys/kernel/debug/tracing/kprobe_events
| # echo 1 &amp;gt; /sys/kernel/debug/tracing/events/kprobes/enable
| Insufficient stack space to handle exception!
| ESR: 0x0000000096000047 -- DABT (curr…&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;arm64: entry: avoid kprobe recursion&lt;/p&gt;
&lt;p&gt;The cortex_a76_erratum_1463225_debug_handler() function is called when
handling debug exceptions (and synchronous exceptions from BRK
instructions), and so is called when a probed function executes. If the
compiler does not inline cortex_a76_erratum_1463225_debug_handler(), it
can be probed.&lt;/p&gt;
&lt;p&gt;If cortex_a76_erratum_1463225_debug_handler() is probed, any debug
exception or software breakpoint exception will result in recursive
exceptions leading to a stack overflow. This can be triggered with the
ftrace multiple_probes selftest, and as per the example splat below.&lt;/p&gt;
&lt;p&gt;This is a regression caused by commit:&lt;/p&gt;
&lt;p&gt;6459b8469753e9fe (&amp;#34;arm64: entry: consolidate Cortex-A76 erratum 1463225 workaround&amp;#34;)&lt;/p&gt;
&lt;p&gt;... which removed the NOKPROBE_SYMBOL() annotation associated with the
function.&lt;/p&gt;
&lt;p&gt;My intent was that cortex_a76_erratum_1463225_debug_handler() would be
inlined into its caller, el1_dbg(), which is marked noinstr and cannot
be probed. Mark cortex_a76_erratum_1463225_debug_handler() as
__always_inline to ensure this.&lt;/p&gt;
&lt;p&gt;Example splat prior to this patch (with recursive entries elided):&lt;/p&gt;
&lt;p&gt;| # echo p cortex_a76_erratum_1463225_debug_handler &amp;gt; /sys/kernel/debug/tracing/kprobe_events
| # echo p do_el0_svc &amp;gt;&amp;gt; /sys/kernel/debug/tracing/kprobe_events
| # echo 1 &amp;gt; /sys/kernel/debug/tracing/events/kprobes/enable
| Insufficient stack space to handle exception!
| ESR: 0x0000000096000047 -- DABT (curr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49888</guid>
    </item>
    <item>
      <title>GHSA-w77p-v2rp-vmv8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w77p-v2rp-vmv8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64: entry: avoid kprobe recursion&lt;/p&gt;
&lt;p&gt;The cortex_a76_erratum_1463225_debug_handler() function is called when
handling debug exceptions (and synchronous exceptions from BRK
instructions), and so is called when a probed function executes. If the
compiler does not inline cortex_a76_erratum_1463225_debug_handler(), it
can be probed.&lt;/p&gt;
&lt;p&gt;If cortex_a76_erratum_1463225_debug_handler() is probed, any debug
exception or software breakpoint exception will result in recursive
exceptions leading to a stack overflow. This can be triggered with the
ftrace multiple_probes selftest, and as per the example splat below.&lt;/p&gt;
&lt;p&gt;This is a regression caused by commit:&lt;/p&gt;
&lt;p&gt;6459b8469753e9fe (&amp;#34;arm64: entry: consolidate Cortex-A76 erratum 1463225 workaround&amp;#34;)&lt;/p&gt;
&lt;p&gt;... which removed the NOKPROBE_SYMBOL() annotation associated with the
function.&lt;/p&gt;
&lt;p&gt;My intent was that cortex_a76_erratum_1463225_debug_handler() would be
inlined into its caller, el1_dbg(), which is marked noinstr and cannot
be probed. Mark cortex_a76_erratum_1463225_debug_handler() as
__always_inline to ensure this.&lt;/p&gt;
&lt;p&gt;Example splat prior to this patch (with recursive entries elided):&lt;/p&gt;
&lt;p&gt;| # echo p cortex_a76_erratum_1463225_debug_handler &amp;gt; /sys/kernel/debug/tracing/kprobe_events
| # echo p do_el0_svc &amp;gt;&amp;gt; /sys/kernel/debug/tracing/kprobe_events
| # echo 1 &amp;gt; /sys/kernel/debug/tracing/events/kprobes/enable
| Insufficient stack space to handle exception!
| ESR: 0x0000000096000047 -- DABT (curr…&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;arm64: entry: avoid kprobe recursion&lt;/p&gt;
&lt;p&gt;The cortex_a76_erratum_1463225_debug_handler() function is called when
handling debug exceptions (and synchronous exceptions from BRK
instructions), and so is called when a probed function executes. If the
compiler does not inline cortex_a76_erratum_1463225_debug_handler(), it
can be probed.&lt;/p&gt;
&lt;p&gt;If cortex_a76_erratum_1463225_debug_handler() is probed, any debug
exception or software breakpoint exception will result in recursive
exceptions leading to a stack overflow. This can be triggered with the
ftrace multiple_probes selftest, and as per the example splat below.&lt;/p&gt;
&lt;p&gt;This is a regression caused by commit:&lt;/p&gt;
&lt;p&gt;6459b8469753e9fe (&amp;#34;arm64: entry: consolidate Cortex-A76 erratum 1463225 workaround&amp;#34;)&lt;/p&gt;
&lt;p&gt;... which removed the NOKPROBE_SYMBOL() annotation associated with the
function.&lt;/p&gt;
&lt;p&gt;My intent was that cortex_a76_erratum_1463225_debug_handler() would be
inlined into its caller, el1_dbg(), which is marked noinstr and cannot
be probed. Mark cortex_a76_erratum_1463225_debug_handler() as
__always_inline to ensure this.&lt;/p&gt;
&lt;p&gt;Example splat prior to this patch (with recursive entries elided):&lt;/p&gt;
&lt;p&gt;| # echo p cortex_a76_erratum_1463225_debug_handler &amp;gt; /sys/kernel/debug/tracing/kprobe_events
| # echo p do_el0_svc &amp;gt;&amp;gt; /sys/kernel/debug/tracing/kprobe_events
| # echo 1 &amp;gt; /sys/kernel/debug/tracing/events/kprobes/enable
| Insufficient stack space to handle exception!
| ESR: 0x0000000096000047 -- DABT (curr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w77p-v2rp-vmv8</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01918-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01918-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:01918-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49888</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49888</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 93 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: entry: avoid kprobe recursion The cortex_a76_erratum_1463225_debug_handler() function is called when handling debug exceptions (and synchronous exceptions from BRK instructions), and so is called when a probed function executes. If the compiler does not inline cortex_a76_erratum_1463225_debug_handler(), it can be probed. If cortex_a76_erratum_1463225_debug_handler() is probed, any debug exception or software breakpoint exception will result in recursive exceptions leading to a stack overflow. This can be triggered with the ftrace multiple_probes selftest, and as per the example splat below. This is a regression caused by commit:   6459b8469753e9fe (&amp;#34;arm64: entry: consolidate Cortex-A76 erratum 1463225 workaround&amp;#34;) ... which removed the NOKPROBE_SYMBOL() annotation associated with the function. My intent was that cortex_a76_erratum_1463225_debug_handler() would be inlined into its caller, el1_dbg(), which is marked noinstr and cannot be probed. Mark cortex_a76_erratum_1463225_debug_handler() as __always_inline to ensure this. Example splat prior to this patch (with recursive entries elided): | # echo p cortex_a76_erratum_1463225_debug_handler &amp;gt; /sys/kernel/debug/tracing/kprobe_events | # echo p do_el0_svc &amp;gt;&amp;gt; /sys/kernel/debug/tracing/kprobe_events | # echo 1 &amp;gt; /sys/kernel/debug/tracing/events/kprobes/enable | Insufficient stack space to handle exception! | ESR: 0x0000000096000047 -- DABT (current EL) |…&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 93 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: entry: avoid kprobe recursion The cortex_a76_erratum_1463225_debug_handler() function is called when handling debug exceptions (and synchronous exceptions from BRK instructions), and so is called when a probed function executes. If the compiler does not inline cortex_a76_erratum_1463225_debug_handler(), it can be probed. If cortex_a76_erratum_1463225_debug_handler() is probed, any debug exception or software breakpoint exception will result in recursive exceptions leading to a stack overflow. This can be triggered with the ftrace multiple_probes selftest, and as per the example splat below. This is a regression caused by commit:   6459b8469753e9fe (&amp;#34;arm64: entry: consolidate Cortex-A76 erratum 1463225 workaround&amp;#34;) ... which removed the NOKPROBE_SYMBOL() annotation associated with the function. My intent was that cortex_a76_erratum_1463225_debug_handler() would be inlined into its caller, el1_dbg(), which is marked noinstr and cannot be probed. Mark cortex_a76_erratum_1463225_debug_handler() as __always_inline to ensure this. Example splat prior to this patch (with recursive entries elided): | # echo p cortex_a76_erratum_1463225_debug_handler &amp;gt; /sys/kernel/debug/tracing/kprobe_events | # echo p do_el0_svc &amp;gt;&amp;gt; /sys/kernel/debug/tracing/kprobe_events | # echo 1 &amp;gt; /sys/kernel/debug/tracing/events/kprobes/enable | Insufficient stack space to handle exception! | ESR: 0x0000000096000047 -- DABT (current EL) |…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49888</guid>
    </item>
  </channel>
</rss>
