<?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 05:01:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-23319</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-23319</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-2026-23319</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0376 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0376</link>
      <description>certfr-2026-avi-0376</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0376</guid>
    </item>
    <item>
      <title>OESA-2026-2418 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-2418</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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:mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MMWe currently assume that there is at least one VMA in a MM, which isn ttrue.So we might end up having find_vma() return NULL, to then de-referenceNULL.  So properly handle find_vma() returning NULL.This fixes the report:Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTIKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline]RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194Code: ...RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8FS:  00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0DR0…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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:mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MMWe currently assume that there is at least one VMA in a MM, which isn ttrue.So we might end up having find_vma() return NULL, to then de-referenceNULL.  So properly handle find_vma() returning NULL.This fixes the report:Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTIKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline]RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194Code: ...RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8FS:  00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0DR0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-2418</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23319</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23319</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 141 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim The root cause of this bug is that when &amp;#39;bpf_link_put&amp;#39; reduces the refcount of &amp;#39;shim_link-&amp;gt;link.link&amp;#39; to zero, the resource is considered released but may still be referenced via &amp;#39;tr-&amp;gt;progs_hlist&amp;#39; in &amp;#39;cgroup_shim_find&amp;#39;. The actual cleanup of &amp;#39;tr-&amp;gt;progs_hlist&amp;#39; in &amp;#39;bpf_shim_tramp_link_release&amp;#39; is deferred. During this window, another process can cause a use-after-free via &amp;#39;bpf_trampoline_link_cgroup_shim&amp;#39;. Based on Martin KaFai Lau&amp;#39;s suggestions, I have created a simple patch. To fix this:    Add an atomic non-zero check in &amp;#39;bpf_trampoline_link_cgroup_shim&amp;#39;.    Only increment the refcount if it is not already zero. Testing:    I verified the fix by adding a delay in    &amp;#39;bpf_shim_tramp_link_release&amp;#39; to make the bug easier to trigger: static void bpf_shim_tramp_link_release(struct bpf_link *link) { 	/* ... */ 	if (!shim_link-&amp;gt;trampoline) 		return; +	msleep(100); 	WARN_ON_ONCE(bpf_trampoline_unlink_prog(&amp;amp;shim_link-&amp;gt;link, 		shim_link-&amp;gt;trampoline, NULL)); 	bpf_trampoline_put(shim_link-&amp;gt;trampoline); } Before the patch, running a PoC easily reproduced the crash(almost 100%) with a call trace similar to KaiyanM&amp;#39;s report. After the patch, the bug no longer occurs even after millions of iterations.&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 141 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim The root cause of this bug is that when &amp;#39;bpf_link_put&amp;#39; reduces the refcount of &amp;#39;shim_link-&amp;gt;link.link&amp;#39; to zero, the resource is considered released but may still be referenced via &amp;#39;tr-&amp;gt;progs_hlist&amp;#39; in &amp;#39;cgroup_shim_find&amp;#39;. The actual cleanup of &amp;#39;tr-&amp;gt;progs_hlist&amp;#39; in &amp;#39;bpf_shim_tramp_link_release&amp;#39; is deferred. During this window, another process can cause a use-after-free via &amp;#39;bpf_trampoline_link_cgroup_shim&amp;#39;. Based on Martin KaFai Lau&amp;#39;s suggestions, I have created a simple patch. To fix this:    Add an atomic non-zero check in &amp;#39;bpf_trampoline_link_cgroup_shim&amp;#39;.    Only increment the refcount if it is not already zero. Testing:    I verified the fix by adding a delay in    &amp;#39;bpf_shim_tramp_link_release&amp;#39; to make the bug easier to trigger: static void bpf_shim_tramp_link_release(struct bpf_link *link) { 	/* ... */ 	if (!shim_link-&amp;gt;trampoline) 		return; +	msleep(100); 	WARN_ON_ONCE(bpf_trampoline_unlink_prog(&amp;amp;shim_link-&amp;gt;link, 		shim_link-&amp;gt;trampoline, NULL)); 	bpf_trampoline_put(shim_link-&amp;gt;trampoline); } Before the patch, running a PoC easily reproduced the crash(almost 100%) with a call trace similar to KaiyanM&amp;#39;s report. After the patch, the bug no longer occurs even after millions of iterations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23319</guid>
    </item>
  </channel>
</rss>
