<?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:27:36 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99651</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99651</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/ksm: reset the unstable trees of all nodes&lt;/p&gt;
&lt;p&gt;Each full scan resets ksm_nr_node_ids unstable tree roots. Enabling
merge_across_nodes resets this count to 1, even if per-node roots were
previously allocated.&lt;/p&gt;
&lt;p&gt;So when toggling &amp;#34;merge_across_nodes&amp;#34; 0 -&amp;gt; 1 -&amp;gt; 0, a scan that starts
while the setting is 1 and continues after switching back to 0 can
encounter stale unstable tree roots, resulting in UAF.&lt;/p&gt;
&lt;p&gt;Only root is allowed to change &amp;#34;merge_across_nodes&amp;#34;, and the documented
sequence is: &amp;#34;merge_across_nodes setting can be changed only when there
are no ksm shared pages in the system: set run 2 to unmerge pages first,
then to 1 after changing merge_across_nodes, to remerge according to the
new setting.&amp;#34;&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix it by tracking in ksm_nr_node_ids the actual number of
allocated tree roots.&lt;/p&gt;
&lt;p&gt;remove_all_stable_nodes() and ksm_check_stable_tree() will now scan
more tree roots (skipping the empty ones), which is harmless.&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/ksm: reset the unstable trees of all nodes&lt;/p&gt;
&lt;p&gt;Each full scan resets ksm_nr_node_ids unstable tree roots. Enabling
merge_across_nodes resets this count to 1, even if per-node roots were
previously allocated.&lt;/p&gt;
&lt;p&gt;So when toggling &amp;#34;merge_across_nodes&amp;#34; 0 -&amp;gt; 1 -&amp;gt; 0, a scan that starts
while the setting is 1 and continues after switching back to 0 can
encounter stale unstable tree roots, resulting in UAF.&lt;/p&gt;
&lt;p&gt;Only root is allowed to change &amp;#34;merge_across_nodes&amp;#34;, and the documented
sequence is: &amp;#34;merge_across_nodes setting can be changed only when there
are no ksm shared pages in the system: set run 2 to unmerge pages first,
then to 1 after changing merge_across_nodes, to remerge according to the
new setting.&amp;#34;&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix it by tracking in ksm_nr_node_ids the actual number of
allocated tree roots.&lt;/p&gt;
&lt;p&gt;remove_all_stable_nodes() and ksm_check_stable_tree() will now scan
more tree roots (skipping the empty ones), which is harmless.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99651</guid>
    </item>
    <item>
      <title>GHSA-ppg8-ff2j-7w83</title>
      <link>https://db.gcve.eu/vuln/ghsa-ppg8-ff2j-7w83</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/ksm: reset the unstable trees of all nodes&lt;/p&gt;
&lt;p&gt;Each full scan resets ksm_nr_node_ids unstable tree roots. Enabling
merge_across_nodes resets this count to 1, even if per-node roots were
previously allocated.&lt;/p&gt;
&lt;p&gt;So when toggling &amp;#34;merge_across_nodes&amp;#34; 0 -&amp;gt; 1 -&amp;gt; 0, a scan that starts
while the setting is 1 and continues after switching back to 0 can
encounter stale unstable tree roots, resulting in UAF.&lt;/p&gt;
&lt;p&gt;Only root is allowed to change &amp;#34;merge_across_nodes&amp;#34;, and the documented
sequence is: &amp;#34;merge_across_nodes setting can be changed only when there
are no ksm shared pages in the system: set run 2 to unmerge pages first,
then to 1 after changing merge_across_nodes, to remerge according to the
new setting.&amp;#34;&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix it by tracking in ksm_nr_node_ids the actual number of
allocated tree roots.&lt;/p&gt;
&lt;p&gt;remove_all_stable_nodes() and ksm_check_stable_tree() will now scan
more tree roots (skipping the empty ones), which is harmless.&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/ksm: reset the unstable trees of all nodes&lt;/p&gt;
&lt;p&gt;Each full scan resets ksm_nr_node_ids unstable tree roots. Enabling
merge_across_nodes resets this count to 1, even if per-node roots were
previously allocated.&lt;/p&gt;
&lt;p&gt;So when toggling &amp;#34;merge_across_nodes&amp;#34; 0 -&amp;gt; 1 -&amp;gt; 0, a scan that starts
while the setting is 1 and continues after switching back to 0 can
encounter stale unstable tree roots, resulting in UAF.&lt;/p&gt;
&lt;p&gt;Only root is allowed to change &amp;#34;merge_across_nodes&amp;#34;, and the documented
sequence is: &amp;#34;merge_across_nodes setting can be changed only when there
are no ksm shared pages in the system: set run 2 to unmerge pages first,
then to 1 after changing merge_across_nodes, to remerge according to the
new setting.&amp;#34;&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix it by tracking in ksm_nr_node_ids the actual number of
allocated tree roots.&lt;/p&gt;
&lt;p&gt;remove_all_stable_nodes() and ksm_check_stable_tree() will now scan
more tree roots (skipping the empty ones), which is harmless.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-ppg8-ff2j-7w83</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>
