<?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://127.0.0.1:10001</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, 21 Nov 2026 02:19:13 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-39744</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-39744</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-39744</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — 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://127.0.0.1:10001/vuln/certfr-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>OESA-2026-1337 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-1337</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md/dm-raid: don&amp;amp;apos;t call md_reap_sync_thread() directly&lt;/p&gt;
&lt;p&gt;Currently md_reap_sync_thread() is called from raid_message() directly
without holding &amp;amp;apos;reconfig_mutex&amp;amp;apos;, this is definitely unsafe because
md_reap_sync_thread() can change many fields that is protected by
&amp;amp;apos;reconfig_mutex&amp;amp;apos;.&lt;/p&gt;
&lt;p&gt;However, hold &amp;amp;apos;reconfig_mutex&amp;amp;apos; here is still problematic because this
will cause deadlock, for example, commit 130443d60b1b (&amp;amp;quot;md: refactor
idle/frozen_sync_thread() to fix deadlock&amp;amp;quot;).&lt;/p&gt;
&lt;p&gt;Fix this problem by using stop_sync_thread() to unregister sync_thread,
like md/raid did.(CVE-2024-35808)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86: fix user address masking non-canonical speculation issue&lt;/p&gt;
&lt;p&gt;It turns out that AMD has a &amp;amp;quot;Meltdown Lite(tm)&amp;amp;quot; issue with non-canonical
accesses in kernel space.  And so using just the high bit to decide
whether an access is in user space or kernel space ends up with the good
old &amp;amp;quot;leak speculative data&amp;amp;quot; if you have the right gadget using the
result:&lt;/p&gt;
&lt;p&gt;CVE-2020-12965 “Transient Execution of Non-Canonical Accesses“&lt;/p&gt;
&lt;p&gt;Now, the kernel surrounds the access with a STAC/CLAC pair, and those
instructions end up serializing execution on older Zen architectures,
which closes the speculation window.&lt;/p&gt;
&lt;p&gt;But that was true only up until Zen 5, which renames t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md/dm-raid: don&amp;amp;apos;t call md_reap_sync_thread() directly&lt;/p&gt;
&lt;p&gt;Currently md_reap_sync_thread() is called from raid_message() directly
without holding &amp;amp;apos;reconfig_mutex&amp;amp;apos;, this is definitely unsafe because
md_reap_sync_thread() can change many fields that is protected by
&amp;amp;apos;reconfig_mutex&amp;amp;apos;.&lt;/p&gt;
&lt;p&gt;However, hold &amp;amp;apos;reconfig_mutex&amp;amp;apos; here is still problematic because this
will cause deadlock, for example, commit 130443d60b1b (&amp;amp;quot;md: refactor
idle/frozen_sync_thread() to fix deadlock&amp;amp;quot;).&lt;/p&gt;
&lt;p&gt;Fix this problem by using stop_sync_thread() to unregister sync_thread,
like md/raid did.(CVE-2024-35808)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86: fix user address masking non-canonical speculation issue&lt;/p&gt;
&lt;p&gt;It turns out that AMD has a &amp;amp;quot;Meltdown Lite(tm)&amp;amp;quot; issue with non-canonical
accesses in kernel space.  And so using just the high bit to decide
whether an access is in user space or kernel space ends up with the good
old &amp;amp;quot;leak speculative data&amp;amp;quot; if you have the right gadget using the
result:&lt;/p&gt;
&lt;p&gt;CVE-2020-12965 “Transient Execution of Non-Canonical Accesses“&lt;/p&gt;
&lt;p&gt;Now, the kernel surrounds the access with a STAC/CLAC pair, and those
instructions end up serializing execution on older Zen architectures,
which closes the speculation window.&lt;/p&gt;
&lt;p&gt;But that was true only up until Zen 5, which renames t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-1337</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39744</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39744</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit()   __irq_exit_rcu()     /* in_hardirq() returns false after this */     preempt_count_sub(HARDIRQ_OFFSET)     tick_irq_exit()       tick_nohz_irq_exit() 	    tick_nohz_stop_sched_tick() 	      trace_tick_stop()  /* a bpf prog is hooked on this trace point */ 		   __bpf_trace_tick_stop() 		      bpf_trace_run2() 			    rcu_read_unlock_special()                               /* will send a IPI to itself */ 			      irq_work_queue_on(&amp;amp;rdp-&amp;gt;defer_qs_iw, rdp-&amp;gt;cpu); A simple reproducer can also be obtained by doing the following in tick_irq_exit(). It will hang on boot without the patch:   static inline void tick_irq_exit(void)   {  +	rcu_read_lock();  +	WRITE_ONCE(current-&amp;gt;rcu_read_unlock_special.b.need_qs, true);  +	rcu_read_unlock();  + [neeraj: Apply Frederic&amp;#39;s suggested fix for PREEMPT_RT]&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit()   __irq_exit_rcu()     /* in_hardirq() returns false after this */     preempt_count_sub(HARDIRQ_OFFSET)     tick_irq_exit()       tick_nohz_irq_exit() 	    tick_nohz_stop_sched_tick() 	      trace_tick_stop()  /* a bpf prog is hooked on this trace point */ 		   __bpf_trace_tick_stop() 		      bpf_trace_run2() 			    rcu_read_unlock_special()                               /* will send a IPI to itself */ 			      irq_work_queue_on(&amp;amp;rdp-&amp;gt;defer_qs_iw, rdp-&amp;gt;cpu); A simple reproducer can also be obtained by doing the following in tick_irq_exit(). It will hang on boot without the patch:   static inline void tick_irq_exit(void)   {  +	rcu_read_lock();  +	WRITE_ONCE(current-&amp;gt;rcu_read_unlock_special.b.need_qs, true);  +	rcu_read_unlock();  + [neeraj: Apply Frederic&amp;#39;s suggested fix for PREEMPT_RT]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39744</guid>
    </item>
  </channel>
</rss>
