<?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:54 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99428</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99428</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ocfs2: snapshot dentry names in file and setattr traces&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;ocfs2: stabilize dentry names in file and setattr traces&amp;#34;,
v4.&lt;/p&gt;
&lt;p&gt;Snapshot names at all six users of ocfs2__file_ops and at the separate
setattr event. Patch 1 handles the five ordinary file-operation callers
and setattr. Patch 2 handles release separately to preserve its locked
open-count sample and take the snapshot outside that critical section.&lt;/p&gt;
&lt;p&gt;The release explanation distinguishes its existing RCU lifetime coverage
from name/length consistency. It does not claim that the ordinary
callers&amp;#39; external-name UAF interleaving crosses the held inode spinlock.
The release source change is unchanged from v3.&lt;/p&gt;
&lt;p&gt;Patch 1 also removes the read callback&amp;#39;s redundant NULL-inode check.
The two patches apply independently and leave trace formats unchanged.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;The open, fsync, read, write and splice-read trace calls pass the live
dentry name and length to the shared ocfs2__file_ops event class.
ocfs2_setattr() passes the same unprotected arguments to its own event.
Both events size and copy a __string field separately. A reference to
the dentry does not pin the external storage backing an individual name.&lt;/p&gt;
&lt;p&gt;With an event enabled, a caller can be preempted after loading the name
pointer. A long-to-short rename can then replace the name and reclaim its
old external allocation before the trace callback sizes or copies it,
provided no other…&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;ocfs2: snapshot dentry names in file and setattr traces&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;ocfs2: stabilize dentry names in file and setattr traces&amp;#34;,
v4.&lt;/p&gt;
&lt;p&gt;Snapshot names at all six users of ocfs2__file_ops and at the separate
setattr event. Patch 1 handles the five ordinary file-operation callers
and setattr. Patch 2 handles release separately to preserve its locked
open-count sample and take the snapshot outside that critical section.&lt;/p&gt;
&lt;p&gt;The release explanation distinguishes its existing RCU lifetime coverage
from name/length consistency. It does not claim that the ordinary
callers&amp;#39; external-name UAF interleaving crosses the held inode spinlock.
The release source change is unchanged from v3.&lt;/p&gt;
&lt;p&gt;Patch 1 also removes the read callback&amp;#39;s redundant NULL-inode check.
The two patches apply independently and leave trace formats unchanged.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;The open, fsync, read, write and splice-read trace calls pass the live
dentry name and length to the shared ocfs2__file_ops event class.
ocfs2_setattr() passes the same unprotected arguments to its own event.
Both events size and copy a __string field separately. A reference to
the dentry does not pin the external storage backing an individual name.&lt;/p&gt;
&lt;p&gt;With an event enabled, a caller can be preempted after loading the name
pointer. A long-to-short rename can then replace the name and reclaim its
old external allocation before the trace callback sizes or copies it,
provided no other…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99428</guid>
    </item>
    <item>
      <title>GHSA-x9w7-ch6f-9pqx</title>
      <link>https://db.gcve.eu/vuln/ghsa-x9w7-ch6f-9pqx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ocfs2: snapshot dentry names in file and setattr traces&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;ocfs2: stabilize dentry names in file and setattr traces&amp;#34;,
v4.&lt;/p&gt;
&lt;p&gt;Snapshot names at all six users of ocfs2__file_ops and at the separate
setattr event. Patch 1 handles the five ordinary file-operation callers
and setattr. Patch 2 handles release separately to preserve its locked
open-count sample and take the snapshot outside that critical section.&lt;/p&gt;
&lt;p&gt;The release explanation distinguishes its existing RCU lifetime coverage
from name/length consistency. It does not claim that the ordinary
callers&amp;#39; external-name UAF interleaving crosses the held inode spinlock.
The release source change is unchanged from v3.&lt;/p&gt;
&lt;p&gt;Patch 1 also removes the read callback&amp;#39;s redundant NULL-inode check.
The two patches apply independently and leave trace formats unchanged.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;The open, fsync, read, write and splice-read trace calls pass the live
dentry name and length to the shared ocfs2__file_ops event class.
ocfs2_setattr() passes the same unprotected arguments to its own event.
Both events size and copy a __string field separately. A reference to
the dentry does not pin the external storage backing an individual name.&lt;/p&gt;
&lt;p&gt;With an event enabled, a caller can be preempted after loading the name
pointer. A long-to-short rename can then replace the name and reclaim its
old external allocation before the trace callback sizes or copies it,
provided no other…&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;ocfs2: snapshot dentry names in file and setattr traces&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;ocfs2: stabilize dentry names in file and setattr traces&amp;#34;,
v4.&lt;/p&gt;
&lt;p&gt;Snapshot names at all six users of ocfs2__file_ops and at the separate
setattr event. Patch 1 handles the five ordinary file-operation callers
and setattr. Patch 2 handles release separately to preserve its locked
open-count sample and take the snapshot outside that critical section.&lt;/p&gt;
&lt;p&gt;The release explanation distinguishes its existing RCU lifetime coverage
from name/length consistency. It does not claim that the ordinary
callers&amp;#39; external-name UAF interleaving crosses the held inode spinlock.
The release source change is unchanged from v3.&lt;/p&gt;
&lt;p&gt;Patch 1 also removes the read callback&amp;#39;s redundant NULL-inode check.
The two patches apply independently and leave trace formats unchanged.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;The open, fsync, read, write and splice-read trace calls pass the live
dentry name and length to the shared ocfs2__file_ops event class.
ocfs2_setattr() passes the same unprotected arguments to its own event.
Both events size and copy a __string field separately. A reference to
the dentry does not pin the external storage backing an individual name.&lt;/p&gt;
&lt;p&gt;With an event enabled, a caller can be preempted after loading the name
pointer. A long-to-short rename can then replace the name and reclaim its
old external allocation before the trace callback sizes or copies it,
provided no other…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-x9w7-ch6f-9pqx</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>
