<?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>Thu, 19 Nov 2026 17:15:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-57952 — Revert "libfs: fix infinite directory reads for offset dir"</title>
      <link>https://db.gcve.eu/vuln/cve-2024-57952</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Revert &amp;#34;libfs: fix infinite directory reads for offset dir&amp;#34;&lt;/p&gt;
&lt;p&gt;The current directory offset allocator (based on mtree_alloc_cyclic)
stores the next offset value to return in octx-&amp;gt;next_offset. This
mechanism typically returns values that increase monotonically over
time. Eventually, though, the newly allocated offset value wraps
back to a low number (say, 2) which is smaller than other already-
allocated offset values.&lt;/p&gt;
&lt;p&gt;Yu Kuai &amp;lt;yukuai3@huawei.com&amp;gt; reports that, after commit 64a7ce76fb90
(&amp;#34;libfs: fix infinite directory reads for offset dir&amp;#34;), if a
directory&amp;#39;s offset allocator wraps, existing entries are no longer
visible via readdir/getdents because offset_readdir() stops listing
entries once an entry&amp;#39;s offset is larger than octx-&amp;gt;next_offset.
These entries vanish persistently -- they can be looked up, but will
never again appear in readdir(3) output.&lt;/p&gt;
&lt;p&gt;The reason for this is that the commit treats directory offsets as
monotonically increasing integer values rather than opaque cookies,
and introduces this comparison:&lt;/p&gt;
&lt;p&gt;if (dentry2offset(dentry) &amp;gt;= last_index) {&lt;/p&gt;
&lt;p&gt;On 64-bit platforms, the directory offset value upper bound is
2^63 - 1. Directory offsets will monotonically increase for millions
of years without wrapping.&lt;/p&gt;
&lt;p&gt;On 32-bit platforms, however, LONG_MAX is 2^31 - 1. The allocator
can wrap after only a few weeks (at worst).&lt;/p&gt;
&lt;p&gt;Revert commit 64a7ce76fb90 (&amp;#34;libfs: fix infinite directory reads for
offset dir&amp;#34;) t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Revert &amp;#34;libfs: fix infinite directory reads for offset dir&amp;#34;&lt;/p&gt;
&lt;p&gt;The current directory offset allocator (based on mtree_alloc_cyclic)
stores the next offset value to return in octx-&amp;gt;next_offset. This
mechanism typically returns values that increase monotonically over
time. Eventually, though, the newly allocated offset value wraps
back to a low number (say, 2) which is smaller than other already-
allocated offset values.&lt;/p&gt;
&lt;p&gt;Yu Kuai &amp;lt;yukuai3@huawei.com&amp;gt; reports that, after commit 64a7ce76fb90
(&amp;#34;libfs: fix infinite directory reads for offset dir&amp;#34;), if a
directory&amp;#39;s offset allocator wraps, existing entries are no longer
visible via readdir/getdents because offset_readdir() stops listing
entries once an entry&amp;#39;s offset is larger than octx-&amp;gt;next_offset.
These entries vanish persistently -- they can be looked up, but will
never again appear in readdir(3) output.&lt;/p&gt;
&lt;p&gt;The reason for this is that the commit treats directory offsets as
monotonically increasing integer values rather than opaque cookies,
and introduces this comparison:&lt;/p&gt;
&lt;p&gt;if (dentry2offset(dentry) &amp;gt;= last_index) {&lt;/p&gt;
&lt;p&gt;On 64-bit platforms, the directory offset value upper bound is
2^63 - 1. Directory offsets will monotonically increase for millions
of years without wrapping.&lt;/p&gt;
&lt;p&gt;On 32-bit platforms, however, LONG_MAX is 2^31 - 1. The allocator
can wrap after only a few weeks (at worst).&lt;/p&gt;
&lt;p&gt;Revert commit 64a7ce76fb90 (&amp;#34;libfs: fix infinite directory reads for
offset dir&amp;#34;) t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-57952</guid>
    </item>
    <item>
      <title>USN-7445-1 — linux, linux-aws, linux-gcp, linux-hwe-6.11, linux-lowlatency, linux-lowlatency-hwe-6.11, linux-oem-6.11, linux-oracle,…</title>
      <link>https://db.gcve.eu/vuln/usn-7445-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-lowlatency-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - GPIO subsystem;
  - GPU drivers;
  - IRQ chip drivers;
  - Network drivers;
  - Mellanox network drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - USB Serial drivers;
  - AFS file system;
  - GFS2 file system;
  - File systems infrastructure;
  - Proc file system;
  - SMB network file system;
  - Timer subsystem;
  - Kernel CPU control infrastructure;
  - Memory management;
  - Networking core;
  - Ethtool driver;
  - IEEE 802.15.4 subsystem;
  - Open vSwitch;
  - Network traffic control;
  - VMware vSockets driver;
(CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670,
CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703,
CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691,
CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683,
CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669,
CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702,
CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695,
CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676,
CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693,
CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-lowlatency-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - GPIO subsystem;
  - GPU drivers;
  - IRQ chip drivers;
  - Network drivers;
  - Mellanox network drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - USB Serial drivers;
  - AFS file system;
  - GFS2 file system;
  - File systems infrastructure;
  - Proc file system;
  - SMB network file system;
  - Timer subsystem;
  - Kernel CPU control infrastructure;
  - Memory management;
  - Networking core;
  - Ethtool driver;
  - IEEE 802.15.4 subsystem;
  - Open vSwitch;
  - Network traffic control;
  - VMware vSockets driver;
(CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670,
CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703,
CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691,
CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683,
CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669,
CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702,
CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695,
CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676,
CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693,
CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7445-1</guid>
    </item>
  </channel>
</rss>
