<?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 03:13:04 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-39844</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-39844</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-39844</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>OESA-2025-2465 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2465</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;Bluetooth: hci_conn: Use disable_delayed_work_sync&lt;/p&gt;
&lt;p&gt;This makes use of disable_delayed_work_sync instead
cancel_delayed_work_sync as it not only cancel the ongoing work but also
disables new submit which is disarable since the object holding the work
is about to be freed.(CVE-2024-56591)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().&lt;/p&gt;
&lt;p&gt;fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything
when it fails.&lt;/p&gt;
&lt;p&gt;Commit 7dd73168e273 (&amp;amp;quot;ipv6: Always allocate pcpu memory in a fib6_nh&amp;amp;quot;)
moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()
but forgot to add cleanup for fib6_nh-&amp;amp;gt;nh_common.nhc_pcpu_rth_output in
case it fails to allocate fib6_nh-&amp;amp;gt;rt6i_pcpu, resulting in memleak.&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s call fib_nh_common_release() and clear nhc_pcpu_rth_output in the
error path.&lt;/p&gt;
&lt;p&gt;Note that we can remove the fib6_nh_release() call in nh_create_ipv6()
later in net-next.git.(CVE-2025-22005)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: Fix a couple integer overflows on 32bit systems&lt;/p&gt;
&lt;p&gt;On 32bit systems the &amp;amp;quot;off + sizeof(struct NTFS_DE)&amp;amp;quot; addition can
have an integer wrapping issue.  Fix it by using size_add().(CVE-2025-22081)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been re…&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;Bluetooth: hci_conn: Use disable_delayed_work_sync&lt;/p&gt;
&lt;p&gt;This makes use of disable_delayed_work_sync instead
cancel_delayed_work_sync as it not only cancel the ongoing work but also
disables new submit which is disarable since the object holding the work
is about to be freed.(CVE-2024-56591)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().&lt;/p&gt;
&lt;p&gt;fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything
when it fails.&lt;/p&gt;
&lt;p&gt;Commit 7dd73168e273 (&amp;amp;quot;ipv6: Always allocate pcpu memory in a fib6_nh&amp;amp;quot;)
moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()
but forgot to add cleanup for fib6_nh-&amp;amp;gt;nh_common.nhc_pcpu_rth_output in
case it fails to allocate fib6_nh-&amp;amp;gt;rt6i_pcpu, resulting in memleak.&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s call fib_nh_common_release() and clear nhc_pcpu_rth_output in the
error path.&lt;/p&gt;
&lt;p&gt;Note that we can remove the fib6_nh_release() call in nh_create_ipv6()
later in net-next.git.(CVE-2025-22005)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: Fix a couple integer overflows on 32bit systems&lt;/p&gt;
&lt;p&gt;On 32bit systems the &amp;amp;quot;off + sizeof(struct NTFS_DE)&amp;amp;quot; addition can
have an integer wrapping issue.  Fix it by using size_add().(CVE-2025-22081)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been re…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2465</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39844</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39844</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 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: move page table sync declarations to linux/pgtable.h During our internal testing, we started observing intermittent boot failures when the machine uses 4-level paging and has a large amount of persistent memory:   BUG: unable to handle page fault for address: ffffe70000000034   #PF: supervisor write access in kernel mode   #PF: error_code(0x0002) - not-present page   PGD 0 P4D 0   Oops: 0002 [#1] SMP NOPTI   RIP: 0010:__init_single_page+0x9/0x6d   Call Trace:    &amp;lt;TASK&amp;gt;    __init_zone_device_page+0x17/0x5d    memmap_init_zone_device+0x154/0x1bb    pagemap_range+0x2e0/0x40f    memremap_pages+0x10b/0x2f0    devm_memremap_pages+0x1e/0x60    dev_dax_probe+0xce/0x2ec [device_dax]    dax_bus_probe+0x6d/0xc9    [... snip ...]    &amp;lt;/TASK&amp;gt; It turns out that the kernel panics while initializing vmemmap (struct page array) when the vmemmap region spans two PGD entries, because the new PGD entry is only installed in init_mm.pgd, but not in the page tables of other tasks. And looking at __populate_section_memmap():   if (vmemmap_can_optimize(altmap, pgmap))           // does not sync top level page tables           r = vmemmap_populate_compound_pages(pfn, start, end, nid, pgmap);   else           // sync top level page tables in x86           r = vmemmap_populate(start, end, nid, altmap); In the normal path, vmemmap_populate() in arch/x86/mm/init_64.c synchronizes the top level page table (See commit 9b861528a801 (&amp;#34;x86…&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 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: move page table sync declarations to linux/pgtable.h During our internal testing, we started observing intermittent boot failures when the machine uses 4-level paging and has a large amount of persistent memory:   BUG: unable to handle page fault for address: ffffe70000000034   #PF: supervisor write access in kernel mode   #PF: error_code(0x0002) - not-present page   PGD 0 P4D 0   Oops: 0002 [#1] SMP NOPTI   RIP: 0010:__init_single_page+0x9/0x6d   Call Trace:    &amp;lt;TASK&amp;gt;    __init_zone_device_page+0x17/0x5d    memmap_init_zone_device+0x154/0x1bb    pagemap_range+0x2e0/0x40f    memremap_pages+0x10b/0x2f0    devm_memremap_pages+0x1e/0x60    dev_dax_probe+0xce/0x2ec [device_dax]    dax_bus_probe+0x6d/0xc9    [... snip ...]    &amp;lt;/TASK&amp;gt; It turns out that the kernel panics while initializing vmemmap (struct page array) when the vmemmap region spans two PGD entries, because the new PGD entry is only installed in init_mm.pgd, but not in the page tables of other tasks. And looking at __populate_section_memmap():   if (vmemmap_can_optimize(altmap, pgmap))           // does not sync top level page tables           r = vmemmap_populate_compound_pages(pfn, start, end, nid, pgmap);   else           // sync top level page tables in x86           r = vmemmap_populate(start, end, nid, altmap); In the normal path, vmemmap_populate() in arch/x86/mm/init_64.c synchronizes the top level page table (See commit 9b861528a801 (&amp;#34;x86…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39844</guid>
    </item>
  </channel>
</rss>
