<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T02:19:19.317529+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2025-39744</id>
    <title>BELL-CVE-2025-39744</title>
    <updated>2026-11-21T02:19:19.328770+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2025-39744"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0895</id>
    <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>
    <updated>2026-11-21T02:19:19.328810+00:00</updated>
    <content>certfr-2025-avi-0895</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0895"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-1337</id>
    <title>OESA-2026-1337 — kernel security update</title>
    <updated>2026-11-21T02:19:19.328826+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>md/dm-raid: don&amp;apos;t call md_reap_sync_thread() directly</p>
<p>Currently md_reap_sync_thread() is called from raid_message() directly
without holding &amp;apos;reconfig_mutex&amp;apos;, this is definitely unsafe because
md_reap_sync_thread() can change many fields that is protected by
&amp;apos;reconfig_mutex&amp;apos;.</p>
<p>However, hold &amp;apos;reconfig_mutex&amp;apos; here is still problematic because this
will cause deadlock, for example, commit 130443d60b1b (&amp;quot;md: refactor
idle/frozen_sync_thread() to fix deadlock&amp;quot;).</p>
<p>Fix this problem by using stop_sync_thread() to unregister sync_thread,
like md/raid did.(CVE-2024-35808)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>x86: fix user address masking non-canonical speculation issue</p>
<p>It turns out that AMD has a &amp;quot;Meltdown Lite(tm)&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;quot;leak speculative data&amp;quot; if you have the right gadget using the
result:</p>
<p>CVE-2020-12965 “Transient Execution of Non-Canonical Accesses“</p>
<p>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.</p>
<p>But that was true only up until Zen 5, which renames t…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-1337"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39744</id>
    <title>UBUNTU-CVE-2025-39744</title>
    <updated>2026-11-21T02:19:19.328955+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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;rdp-&gt;defer_qs_iw, rdp-&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-&gt;rcu_read_unlock_special.b.need_qs, true);  +	rcu_read_unlock();  + [neeraj: Apply Frederic's suggested fix for PREEMPT_RT]</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39744"/>
  </entry>
</feed>
