<?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 09:55:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53342</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-53342</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-53342</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1162 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1162</link>
      <description>certfr-2026-avi-1162</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1162</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53342</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53342</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 128 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: mm: call pagetable dtor when freeing hot-removed page tables Since 5e8eb9aeeda3 (&amp;#34;arm64: mm: always call PTE/PMD ctor in __create_pgd_mapping()&amp;#34;) page-table allocation on ARM64 always calls pagetable_{pte,pmd,pud,p4d}_ctor().  This sets the page_type to PGTY_table, increments NR_PAGETABLE and possible allocates a PTL.  However the matching pagetable_dtor() calls were never added. With DEBUG_VM enabled on kernel versions prior to v6.17 without 2dfcd1608f3a9 (&amp;#34;mm/page_alloc: let page freeing clear any set page type&amp;#34;) this leads to the following warning when freeing these pages due to page-&amp;gt;page_type sharing page-&amp;gt;_mapcount:   BUG: Bad page state in process ... pfn:284fbb   page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x284fbb   flags: 0x17fffc000000000(node=0|zone=2|lastcpupid=0x1ffff)   page_type: f2(table)   page dumped because: nonzero mapcount   Call trace:    bad_page+0x13c/0x160    __free_frozen_pages+0x6cc/0x860    ___free_pages+0xf4/0x180    free_pages+0x54/0x80    free_hotplug_page_range.part.0+0x58/0x90    free_empty_tables+0x438/0x500    __remove_pgd_mapping.constprop.0+0x60/0xa8    arch_remove_memory+0x48/0x80    try_remove_memory+0x158/0x1d8    offline_and_remove_memory+0x138/0x180 It can also lead to leaking the ptl allocation if ALLOC_SPLIT_PTLOCKS is defined and incorrect NR_PAGETABLE stats.  Fix this by calling pagetable_dtor() in free_hotplug_pgtable_page() prior…&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 128 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: mm: call pagetable dtor when freeing hot-removed page tables Since 5e8eb9aeeda3 (&amp;#34;arm64: mm: always call PTE/PMD ctor in __create_pgd_mapping()&amp;#34;) page-table allocation on ARM64 always calls pagetable_{pte,pmd,pud,p4d}_ctor().  This sets the page_type to PGTY_table, increments NR_PAGETABLE and possible allocates a PTL.  However the matching pagetable_dtor() calls were never added. With DEBUG_VM enabled on kernel versions prior to v6.17 without 2dfcd1608f3a9 (&amp;#34;mm/page_alloc: let page freeing clear any set page type&amp;#34;) this leads to the following warning when freeing these pages due to page-&amp;gt;page_type sharing page-&amp;gt;_mapcount:   BUG: Bad page state in process ... pfn:284fbb   page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x284fbb   flags: 0x17fffc000000000(node=0|zone=2|lastcpupid=0x1ffff)   page_type: f2(table)   page dumped because: nonzero mapcount   Call trace:    bad_page+0x13c/0x160    __free_frozen_pages+0x6cc/0x860    ___free_pages+0xf4/0x180    free_pages+0x54/0x80    free_hotplug_page_range.part.0+0x58/0x90    free_empty_tables+0x438/0x500    __remove_pgd_mapping.constprop.0+0x60/0xa8    arch_remove_memory+0x48/0x80    try_remove_memory+0x158/0x1d8    offline_and_remove_memory+0x138/0x180 It can also lead to leaking the ptl allocation if ALLOC_SPLIT_PTLOCKS is defined and incorrect NR_PAGETABLE stats.  Fix this by calling pagetable_dtor() in free_hotplug_pgtable_page() prior…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53342</guid>
    </item>
  </channel>
</rss>
