<?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:03:37 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99697</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99697</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: memcontrol: fix NULL pointer deref and UAF from high_work_func() on dying memcg&lt;/p&gt;
&lt;p&gt;When memory.high is exceeded in non-task context, try_charge_memcg()
schedules memcg-&amp;gt;high_work without taking a reference on the memcg, and
high_work_func() invokes reclaim_high() without pinning the memcg.&lt;/p&gt;
&lt;p&gt;With obj_cgroup reparenting, introduced in commit bf4f059954dc (&amp;#34;mm:
memcg/slab: obj_cgroup API&amp;#34;), objects charged to a child memcg are
reparented to its parent in mem_cgroup_css_offline() instead of holding a
reference on the child until uncharged.  Subsequent uncharges of those
objects go to the parent, which can leave the child&amp;#39;s memory use
permanently above its high limit, so any later charge on the offlined
memcg in non-task context schedules high_work.  This was later widened
from kernel memory to LRU folios when commit f1cf8d2f36dc (&amp;#34;mm:
memcontrol: eliminate the problem of dying memory cgroup for LRU folios&amp;#34;)
converted LRU folios to use obj_cgroup reparenting.&lt;/p&gt;
&lt;p&gt;cancel_work_sync(&amp;amp;memcg-&amp;gt;high_work) only runs at the end of teardown in
mem_cgroup_css_free(), so high_work_func() can start or still be running
reclaim_high() after mem_cgroup_css_released() or shrink_many() has called
lru_gen_release_memcg() and unhashed lruvec-&amp;gt;lrugen.list.  If reclaim
tries to rotate the memcg, lru_gen_rotate_memcg() dereferences a NULL
pprev pointer.  This issue is specific to MGLRU and was introduced with
the memcg LRU in commit e4…&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: memcontrol: fix NULL pointer deref and UAF from high_work_func() on dying memcg&lt;/p&gt;
&lt;p&gt;When memory.high is exceeded in non-task context, try_charge_memcg()
schedules memcg-&amp;gt;high_work without taking a reference on the memcg, and
high_work_func() invokes reclaim_high() without pinning the memcg.&lt;/p&gt;
&lt;p&gt;With obj_cgroup reparenting, introduced in commit bf4f059954dc (&amp;#34;mm:
memcg/slab: obj_cgroup API&amp;#34;), objects charged to a child memcg are
reparented to its parent in mem_cgroup_css_offline() instead of holding a
reference on the child until uncharged.  Subsequent uncharges of those
objects go to the parent, which can leave the child&amp;#39;s memory use
permanently above its high limit, so any later charge on the offlined
memcg in non-task context schedules high_work.  This was later widened
from kernel memory to LRU folios when commit f1cf8d2f36dc (&amp;#34;mm:
memcontrol: eliminate the problem of dying memory cgroup for LRU folios&amp;#34;)
converted LRU folios to use obj_cgroup reparenting.&lt;/p&gt;
&lt;p&gt;cancel_work_sync(&amp;amp;memcg-&amp;gt;high_work) only runs at the end of teardown in
mem_cgroup_css_free(), so high_work_func() can start or still be running
reclaim_high() after mem_cgroup_css_released() or shrink_many() has called
lru_gen_release_memcg() and unhashed lruvec-&amp;gt;lrugen.list.  If reclaim
tries to rotate the memcg, lru_gen_rotate_memcg() dereferences a NULL
pprev pointer.  This issue is specific to MGLRU and was introduced with
the memcg LRU in commit e4…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99697</guid>
    </item>
    <item>
      <title>GHSA-76j9-mfj4-8h8p</title>
      <link>https://db.gcve.eu/vuln/ghsa-76j9-mfj4-8h8p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: memcontrol: fix NULL pointer deref and UAF from high_work_func() on dying memcg&lt;/p&gt;
&lt;p&gt;When memory.high is exceeded in non-task context, try_charge_memcg()
schedules memcg-&amp;gt;high_work without taking a reference on the memcg, and
high_work_func() invokes reclaim_high() without pinning the memcg.&lt;/p&gt;
&lt;p&gt;With obj_cgroup reparenting, introduced in commit bf4f059954dc (&amp;#34;mm:
memcg/slab: obj_cgroup API&amp;#34;), objects charged to a child memcg are
reparented to its parent in mem_cgroup_css_offline() instead of holding a
reference on the child until uncharged.  Subsequent uncharges of those
objects go to the parent, which can leave the child&amp;#39;s memory use
permanently above its high limit, so any later charge on the offlined
memcg in non-task context schedules high_work.  This was later widened
from kernel memory to LRU folios when commit f1cf8d2f36dc (&amp;#34;mm:
memcontrol: eliminate the problem of dying memory cgroup for LRU folios&amp;#34;)
converted LRU folios to use obj_cgroup reparenting.&lt;/p&gt;
&lt;p&gt;cancel_work_sync(&amp;amp;memcg-&amp;gt;high_work) only runs at the end of teardown in
mem_cgroup_css_free(), so high_work_func() can start or still be running
reclaim_high() after mem_cgroup_css_released() or shrink_many() has called
lru_gen_release_memcg() and unhashed lruvec-&amp;gt;lrugen.list.  If reclaim
tries to rotate the memcg, lru_gen_rotate_memcg() dereferences a NULL
pprev pointer.  This issue is specific to MGLRU and was introduced with
the memcg LRU in commit e4…&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: memcontrol: fix NULL pointer deref and UAF from high_work_func() on dying memcg&lt;/p&gt;
&lt;p&gt;When memory.high is exceeded in non-task context, try_charge_memcg()
schedules memcg-&amp;gt;high_work without taking a reference on the memcg, and
high_work_func() invokes reclaim_high() without pinning the memcg.&lt;/p&gt;
&lt;p&gt;With obj_cgroup reparenting, introduced in commit bf4f059954dc (&amp;#34;mm:
memcg/slab: obj_cgroup API&amp;#34;), objects charged to a child memcg are
reparented to its parent in mem_cgroup_css_offline() instead of holding a
reference on the child until uncharged.  Subsequent uncharges of those
objects go to the parent, which can leave the child&amp;#39;s memory use
permanently above its high limit, so any later charge on the offlined
memcg in non-task context schedules high_work.  This was later widened
from kernel memory to LRU folios when commit f1cf8d2f36dc (&amp;#34;mm:
memcontrol: eliminate the problem of dying memory cgroup for LRU folios&amp;#34;)
converted LRU folios to use obj_cgroup reparenting.&lt;/p&gt;
&lt;p&gt;cancel_work_sync(&amp;amp;memcg-&amp;gt;high_work) only runs at the end of teardown in
mem_cgroup_css_free(), so high_work_func() can start or still be running
reclaim_high() after mem_cgroup_css_released() or shrink_many() has called
lru_gen_release_memcg() and unhashed lruvec-&amp;gt;lrugen.list.  If reclaim
tries to rotate the memcg, lru_gen_rotate_memcg() dereferences a NULL
pprev pointer.  This issue is specific to MGLRU and was introduced with
the memcg LRU in commit e4…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-76j9-mfj4-8h8p</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>
