<?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:19 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99736</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99736</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/shmem: fix accounting of swapin-error markers&lt;/p&gt;
&lt;p&gt;A failed swap read replaces the swap entry with a swapin-error marker in
the page-cache and subtracts its pages from &amp;#34;alloced&amp;#34; and &amp;#34;swapped&amp;#34;;
however, it leaves their block charge in place.&lt;/p&gt;
&lt;p&gt;Removing the marker during truncate then subtracts from &amp;#34;swapped&amp;#34; again.
This can underflow the counters or make swapped reach zero while other
pages remain swapped out, causing swapoff to loop without finding them.&lt;/p&gt;
&lt;p&gt;When installing the marker, subtract only from &amp;#34;swapped&amp;#34; and let
shmem_recalc_inode() reduce &amp;#34;alloced&amp;#34; and release the block charge.&lt;/p&gt;
&lt;p&gt;Make shmem_free_swap() report successful removal separately from the
number of swap pages freed, so removing a swapin-error marker does not
subtract from &amp;#34;swapped&amp;#34; again.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a bit confusing, but replacing a swapped out page by a swapin-error
marker in shmem_set_folio_swapin_error() behaves as follows:&lt;/p&gt;
&lt;p&gt;Initially:
	alloced=1, swapped=1, nrpages=0
Calling shmem_recalc_inode(inode, 0, -1)
	-&amp;gt; swapped = 0
	-&amp;gt; freed =  1 - 0 - 0 = 1
	-&amp;gt; alloced -= freed
	-&amp;gt; alloced=0, swapped=0, block charge released&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/shmem: fix accounting of swapin-error markers&lt;/p&gt;
&lt;p&gt;A failed swap read replaces the swap entry with a swapin-error marker in
the page-cache and subtracts its pages from &amp;#34;alloced&amp;#34; and &amp;#34;swapped&amp;#34;;
however, it leaves their block charge in place.&lt;/p&gt;
&lt;p&gt;Removing the marker during truncate then subtracts from &amp;#34;swapped&amp;#34; again.
This can underflow the counters or make swapped reach zero while other
pages remain swapped out, causing swapoff to loop without finding them.&lt;/p&gt;
&lt;p&gt;When installing the marker, subtract only from &amp;#34;swapped&amp;#34; and let
shmem_recalc_inode() reduce &amp;#34;alloced&amp;#34; and release the block charge.&lt;/p&gt;
&lt;p&gt;Make shmem_free_swap() report successful removal separately from the
number of swap pages freed, so removing a swapin-error marker does not
subtract from &amp;#34;swapped&amp;#34; again.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a bit confusing, but replacing a swapped out page by a swapin-error
marker in shmem_set_folio_swapin_error() behaves as follows:&lt;/p&gt;
&lt;p&gt;Initially:
	alloced=1, swapped=1, nrpages=0
Calling shmem_recalc_inode(inode, 0, -1)
	-&amp;gt; swapped = 0
	-&amp;gt; freed =  1 - 0 - 0 = 1
	-&amp;gt; alloced -= freed
	-&amp;gt; alloced=0, swapped=0, block charge released&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99736</guid>
    </item>
    <item>
      <title>GHSA-52wv-694g-rq98</title>
      <link>https://db.gcve.eu/vuln/ghsa-52wv-694g-rq98</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/shmem: fix accounting of swapin-error markers&lt;/p&gt;
&lt;p&gt;A failed swap read replaces the swap entry with a swapin-error marker in
the page-cache and subtracts its pages from &amp;#34;alloced&amp;#34; and &amp;#34;swapped&amp;#34;;
however, it leaves their block charge in place.&lt;/p&gt;
&lt;p&gt;Removing the marker during truncate then subtracts from &amp;#34;swapped&amp;#34; again.
This can underflow the counters or make swapped reach zero while other
pages remain swapped out, causing swapoff to loop without finding them.&lt;/p&gt;
&lt;p&gt;When installing the marker, subtract only from &amp;#34;swapped&amp;#34; and let
shmem_recalc_inode() reduce &amp;#34;alloced&amp;#34; and release the block charge.&lt;/p&gt;
&lt;p&gt;Make shmem_free_swap() report successful removal separately from the
number of swap pages freed, so removing a swapin-error marker does not
subtract from &amp;#34;swapped&amp;#34; again.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a bit confusing, but replacing a swapped out page by a swapin-error
marker in shmem_set_folio_swapin_error() behaves as follows:&lt;/p&gt;
&lt;p&gt;Initially:
	alloced=1, swapped=1, nrpages=0
Calling shmem_recalc_inode(inode, 0, -1)
	-&amp;gt; swapped = 0
	-&amp;gt; freed =  1 - 0 - 0 = 1
	-&amp;gt; alloced -= freed
	-&amp;gt; alloced=0, swapped=0, block charge released&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/shmem: fix accounting of swapin-error markers&lt;/p&gt;
&lt;p&gt;A failed swap read replaces the swap entry with a swapin-error marker in
the page-cache and subtracts its pages from &amp;#34;alloced&amp;#34; and &amp;#34;swapped&amp;#34;;
however, it leaves their block charge in place.&lt;/p&gt;
&lt;p&gt;Removing the marker during truncate then subtracts from &amp;#34;swapped&amp;#34; again.
This can underflow the counters or make swapped reach zero while other
pages remain swapped out, causing swapoff to loop without finding them.&lt;/p&gt;
&lt;p&gt;When installing the marker, subtract only from &amp;#34;swapped&amp;#34; and let
shmem_recalc_inode() reduce &amp;#34;alloced&amp;#34; and release the block charge.&lt;/p&gt;
&lt;p&gt;Make shmem_free_swap() report successful removal separately from the
number of swap pages freed, so removing a swapin-error marker does not
subtract from &amp;#34;swapped&amp;#34; again.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a bit confusing, but replacing a swapped out page by a swapin-error
marker in shmem_set_folio_swapin_error() behaves as follows:&lt;/p&gt;
&lt;p&gt;Initially:
	alloced=1, swapped=1, nrpages=0
Calling shmem_recalc_inode(inode, 0, -1)
	-&amp;gt; swapped = 0
	-&amp;gt; freed =  1 - 0 - 0 = 1
	-&amp;gt; alloced -= freed
	-&amp;gt; alloced=0, swapped=0, block charge released&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-52wv-694g-rq98</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>
