<?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 00:37:29 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-39913</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-39913</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-39913</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0894 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0894</link>
      <description>certfr-2025-avi-0894</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0894</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-39913</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39913</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 188 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-&amp;gt;cork. syzbot reported the splat below. [0] The repro does the following:   1. Load a sk_msg prog that calls bpf_msg_cork_bytes(msg, cork_bytes)   2. Attach the prog to a SOCKMAP   3. Add a socket to the SOCKMAP   4. Activate fault injection   5. Send data less than cork_bytes At 5., the data is carried over to the next sendmsg() as it is smaller than the cork_bytes specified by bpf_msg_cork_bytes(). Then, tcp_bpf_send_verdict() tries to allocate psock-&amp;gt;cork to hold the data, but this fails silently due to fault injection + __GFP_NOWARN. If the allocation fails, we need to revert the sk-&amp;gt;sk_forward_alloc change done by sk_msg_alloc(). Let&amp;#39;s call sk_msg_free() when tcp_bpf_send_verdict fails to allocate psock-&amp;gt;cork. The &amp;#34;*copied&amp;#34; also needs to be updated such that a proper error can be returned to the caller, sendmsg. It fails to allocate psock-&amp;gt;cork. Nothing has been corked so far, so this patch simply sets &amp;#34;*copied&amp;#34; to 0. [0]: WARNING: net/ipv4/af_inet.c:156 at inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156, CPU#1: syz-executor/5983 Modules linked in: CPU: 1 UID: 0 PID: 5983 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156 Code: 0f 0b 90 e9 62 fe ff ff e8 7a db…&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 188 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-&amp;gt;cork. syzbot reported the splat below. [0] The repro does the following:   1. Load a sk_msg prog that calls bpf_msg_cork_bytes(msg, cork_bytes)   2. Attach the prog to a SOCKMAP   3. Add a socket to the SOCKMAP   4. Activate fault injection   5. Send data less than cork_bytes At 5., the data is carried over to the next sendmsg() as it is smaller than the cork_bytes specified by bpf_msg_cork_bytes(). Then, tcp_bpf_send_verdict() tries to allocate psock-&amp;gt;cork to hold the data, but this fails silently due to fault injection + __GFP_NOWARN. If the allocation fails, we need to revert the sk-&amp;gt;sk_forward_alloc change done by sk_msg_alloc(). Let&amp;#39;s call sk_msg_free() when tcp_bpf_send_verdict fails to allocate psock-&amp;gt;cork. The &amp;#34;*copied&amp;#34; also needs to be updated such that a proper error can be returned to the caller, sendmsg. It fails to allocate psock-&amp;gt;cork. Nothing has been corked so far, so this patch simply sets &amp;#34;*copied&amp;#34; to 0. [0]: WARNING: net/ipv4/af_inet.c:156 at inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156, CPU#1: syz-executor/5983 Modules linked in: CPU: 1 UID: 0 PID: 5983 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156 Code: 0f 0b 90 e9 62 fe ff ff e8 7a db…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39913</guid>
    </item>
  </channel>
</rss>
