<?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://db.gcve.eu</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>Fri, 20 Nov 2026 21:31:05 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99659</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99659</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mmu_gather: fix flushing ranges with 4 GiB or larger&lt;/p&gt;
&lt;p&gt;__tlb_adjust_range() takes the size of the range which has to be flushed
as an unsigned int. Its callers, tlb_flush_{pte,pmd,pud,p4d}_range(), get
and pass an unsigned long. Consequently, a range that is 4 GiB or larger
gets truncated, possibly to 0.&lt;/p&gt;
&lt;p&gt;On arm64 with hugetlb, a 64k kernel can have 16 GiB hugetlb folios
mapped contiguously at the PMD level and flush them when unmapping, and a
16k kernel can flush 64 GiB PUDs through tlb_unshare_pmd_ptdesc(). So
at least these two scenarios are affected.&lt;/p&gt;
&lt;p&gt;Fix it by flushing the proper range instead of the truncated one by
properly using &amp;#34;unsigned long&amp;#34; for range_size.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: use two-tab indent, simplify description ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mmu_gather: fix flushing ranges with 4 GiB or larger&lt;/p&gt;
&lt;p&gt;__tlb_adjust_range() takes the size of the range which has to be flushed
as an unsigned int. Its callers, tlb_flush_{pte,pmd,pud,p4d}_range(), get
and pass an unsigned long. Consequently, a range that is 4 GiB or larger
gets truncated, possibly to 0.&lt;/p&gt;
&lt;p&gt;On arm64 with hugetlb, a 64k kernel can have 16 GiB hugetlb folios
mapped contiguously at the PMD level and flush them when unmapping, and a
16k kernel can flush 64 GiB PUDs through tlb_unshare_pmd_ptdesc(). So
at least these two scenarios are affected.&lt;/p&gt;
&lt;p&gt;Fix it by flushing the proper range instead of the truncated one by
properly using &amp;#34;unsigned long&amp;#34; for range_size.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: use two-tab indent, simplify description ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99659</guid>
    </item>
    <item>
      <title>GHSA-566v-r6wp-3fcr</title>
      <link>https://db.gcve.eu/vuln/ghsa-566v-r6wp-3fcr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mmu_gather: fix flushing ranges with 4 GiB or larger&lt;/p&gt;
&lt;p&gt;__tlb_adjust_range() takes the size of the range which has to be flushed
as an unsigned int. Its callers, tlb_flush_{pte,pmd,pud,p4d}_range(), get
and pass an unsigned long. Consequently, a range that is 4 GiB or larger
gets truncated, possibly to 0.&lt;/p&gt;
&lt;p&gt;On arm64 with hugetlb, a 64k kernel can have 16 GiB hugetlb folios
mapped contiguously at the PMD level and flush them when unmapping, and a
16k kernel can flush 64 GiB PUDs through tlb_unshare_pmd_ptdesc(). So
at least these two scenarios are affected.&lt;/p&gt;
&lt;p&gt;Fix it by flushing the proper range instead of the truncated one by
properly using &amp;#34;unsigned long&amp;#34; for range_size.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: use two-tab indent, simplify description ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mmu_gather: fix flushing ranges with 4 GiB or larger&lt;/p&gt;
&lt;p&gt;__tlb_adjust_range() takes the size of the range which has to be flushed
as an unsigned int. Its callers, tlb_flush_{pte,pmd,pud,p4d}_range(), get
and pass an unsigned long. Consequently, a range that is 4 GiB or larger
gets truncated, possibly to 0.&lt;/p&gt;
&lt;p&gt;On arm64 with hugetlb, a 64k kernel can have 16 GiB hugetlb folios
mapped contiguously at the PMD level and flush them when unmapping, and a
16k kernel can flush 64 GiB PUDs through tlb_unshare_pmd_ptdesc(). So
at least these two scenarios are affected.&lt;/p&gt;
&lt;p&gt;Fix it by flushing the proper range instead of the truncated one by
properly using &amp;#34;unsigned long&amp;#34; for range_size.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: use two-tab indent, simplify description ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-566v-r6wp-3fcr</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
