<?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:04:09 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99648</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99648</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/vma: call -&amp;gt;may_split() before a partial merge&lt;/p&gt;
&lt;p&gt;A driver can use the -&amp;gt;may_split() hook to forbid a VMA boundary at
certain addresses.&lt;/p&gt;
&lt;p&gt;A device-dax device is a character device that gives raw access to a
range of memory through mmap(). device-dax refuses any address that is not
a multiple of the device&amp;#39;s alignment through vm_ops-&amp;gt;may_split.&lt;/p&gt;
&lt;p&gt;vma_merge_existing_range() can move boundaries, but does not call
vm_ops-&amp;gt;may_split.&lt;/p&gt;
&lt;p&gt;If a range at the edge of a VMA gets the attributes of the adjacent VMA,
the function moves only that range over to the neighbour: one VMA shrinks
and the other grows. This is a partial merge, and vma_modify() tries it
before any split.&lt;/p&gt;
&lt;p&gt;Take a device-dax VMA that lies next to another VMA of the same file.
The user calls mprotect() on the one page of the first VMA that touches
the second VMA, and asks for the protection that the second VMA already
has. The result is a partial merge. It puts the boundary inside a 1 GiB
mapping, which is a single leaf entry at the PUD level.&lt;/p&gt;
&lt;p&gt;As part of the merge, the kernel looks for a huge PMD to split at the
new boundary. That code does not expect a PUD leaf:&lt;/p&gt;
&lt;p&gt;vma_merge_existing_range()
      commit_merge()
        vma_adjust_trans_huge()
          split_huge_pmd_address()
            mm_find_pmd()
              treats the PUD leaf as a pointer to a PMD table,
              so the &amp;#34;table&amp;#34; is the device memory that the leaf maps
            __s…&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/vma: call -&amp;gt;may_split() before a partial merge&lt;/p&gt;
&lt;p&gt;A driver can use the -&amp;gt;may_split() hook to forbid a VMA boundary at
certain addresses.&lt;/p&gt;
&lt;p&gt;A device-dax device is a character device that gives raw access to a
range of memory through mmap(). device-dax refuses any address that is not
a multiple of the device&amp;#39;s alignment through vm_ops-&amp;gt;may_split.&lt;/p&gt;
&lt;p&gt;vma_merge_existing_range() can move boundaries, but does not call
vm_ops-&amp;gt;may_split.&lt;/p&gt;
&lt;p&gt;If a range at the edge of a VMA gets the attributes of the adjacent VMA,
the function moves only that range over to the neighbour: one VMA shrinks
and the other grows. This is a partial merge, and vma_modify() tries it
before any split.&lt;/p&gt;
&lt;p&gt;Take a device-dax VMA that lies next to another VMA of the same file.
The user calls mprotect() on the one page of the first VMA that touches
the second VMA, and asks for the protection that the second VMA already
has. The result is a partial merge. It puts the boundary inside a 1 GiB
mapping, which is a single leaf entry at the PUD level.&lt;/p&gt;
&lt;p&gt;As part of the merge, the kernel looks for a huge PMD to split at the
new boundary. That code does not expect a PUD leaf:&lt;/p&gt;
&lt;p&gt;vma_merge_existing_range()
      commit_merge()
        vma_adjust_trans_huge()
          split_huge_pmd_address()
            mm_find_pmd()
              treats the PUD leaf as a pointer to a PMD table,
              so the &amp;#34;table&amp;#34; is the device memory that the leaf maps
            __s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99648</guid>
    </item>
    <item>
      <title>GHSA-fghq-jfcc-9rj7</title>
      <link>https://db.gcve.eu/vuln/ghsa-fghq-jfcc-9rj7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/vma: call -&amp;gt;may_split() before a partial merge&lt;/p&gt;
&lt;p&gt;A driver can use the -&amp;gt;may_split() hook to forbid a VMA boundary at
certain addresses.&lt;/p&gt;
&lt;p&gt;A device-dax device is a character device that gives raw access to a
range of memory through mmap(). device-dax refuses any address that is not
a multiple of the device&amp;#39;s alignment through vm_ops-&amp;gt;may_split.&lt;/p&gt;
&lt;p&gt;vma_merge_existing_range() can move boundaries, but does not call
vm_ops-&amp;gt;may_split.&lt;/p&gt;
&lt;p&gt;If a range at the edge of a VMA gets the attributes of the adjacent VMA,
the function moves only that range over to the neighbour: one VMA shrinks
and the other grows. This is a partial merge, and vma_modify() tries it
before any split.&lt;/p&gt;
&lt;p&gt;Take a device-dax VMA that lies next to another VMA of the same file.
The user calls mprotect() on the one page of the first VMA that touches
the second VMA, and asks for the protection that the second VMA already
has. The result is a partial merge. It puts the boundary inside a 1 GiB
mapping, which is a single leaf entry at the PUD level.&lt;/p&gt;
&lt;p&gt;As part of the merge, the kernel looks for a huge PMD to split at the
new boundary. That code does not expect a PUD leaf:&lt;/p&gt;
&lt;p&gt;vma_merge_existing_range()
      commit_merge()
        vma_adjust_trans_huge()
          split_huge_pmd_address()
            mm_find_pmd()
              treats the PUD leaf as a pointer to a PMD table,
              so the &amp;#34;table&amp;#34; is the device memory that the leaf maps
            __s…&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/vma: call -&amp;gt;may_split() before a partial merge&lt;/p&gt;
&lt;p&gt;A driver can use the -&amp;gt;may_split() hook to forbid a VMA boundary at
certain addresses.&lt;/p&gt;
&lt;p&gt;A device-dax device is a character device that gives raw access to a
range of memory through mmap(). device-dax refuses any address that is not
a multiple of the device&amp;#39;s alignment through vm_ops-&amp;gt;may_split.&lt;/p&gt;
&lt;p&gt;vma_merge_existing_range() can move boundaries, but does not call
vm_ops-&amp;gt;may_split.&lt;/p&gt;
&lt;p&gt;If a range at the edge of a VMA gets the attributes of the adjacent VMA,
the function moves only that range over to the neighbour: one VMA shrinks
and the other grows. This is a partial merge, and vma_modify() tries it
before any split.&lt;/p&gt;
&lt;p&gt;Take a device-dax VMA that lies next to another VMA of the same file.
The user calls mprotect() on the one page of the first VMA that touches
the second VMA, and asks for the protection that the second VMA already
has. The result is a partial merge. It puts the boundary inside a 1 GiB
mapping, which is a single leaf entry at the PUD level.&lt;/p&gt;
&lt;p&gt;As part of the merge, the kernel looks for a huge PMD to split at the
new boundary. That code does not expect a PUD leaf:&lt;/p&gt;
&lt;p&gt;vma_merge_existing_range()
      commit_merge()
        vma_adjust_trans_huge()
          split_huge_pmd_address()
            mm_find_pmd()
              treats the PUD leaf as a pointer to a PMD table,
              so the &amp;#34;table&amp;#34; is the device memory that the leaf maps
            __s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-fghq-jfcc-9rj7</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>
