<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-27T10:23:42.122016+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-98941</id>
    <title>CVE-2026-98941 — ext4: don't enable large folios on encrypted inodes</title>
    <updated>2026-10-27T10:23:42.133722+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ext4: don't enable large folios on encrypted inodes</p>
<p>Commit 709f0f1f1bf5 ("ext4: add checks for large folio
incompatibilities when BS &gt; PS") disables large folios at mount time
if the "encrypt" feature is set. However, enabling that feature on a
mounted filesystem circumvents that check, and writing encrypted data
results in a crash:</p>
<p>BUG: kernel NULL pointer dereference, address: 0000000000000028
  Workqueue: ext4-rsv-conversion ext4_end_io_rsv_work
  RIP: 0010:ext4_finish_bio+0xf7/0x3e0
  Call Trace:
   ext4_release_io_end+0x51/0x110
   ext4_end_io_end+0x4c/0xe0
   ext4_end_io_rsv_work+0xb3/0x100</p>
<p>Fix this by disabling large folios on encrypted inodes, as is
already done for inodes that use data journaling.</p>
<p>This affects all kernels between v6.19 and v7.2, but it is not needed
in v7.3, where the code was significantly refactored.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98941"/>
  </entry>
</feed>
