<?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:31:14 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99755</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99755</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked&lt;/p&gt;
&lt;p&gt;extts_fifo_show() walks ptp-&amp;gt;tsevqs with list_count_nodes() and then
list_first_entry() without holding ptp-&amp;gt;tsevqs_lock, the spinlock that
&amp;#34;protects tsevqs from concurrent access&amp;#34;. Every other accessor of the
list honours it: ptp_open() (list_add_tail), ptp_release() (list_del
followed by kfree of the per-fd queue), ptp_clock_release() and
ptp_clock_event() all take tsevqs_lock. extts_fifo_show() is the only
one that does not.&lt;/p&gt;
&lt;p&gt;A per-fd timestamp queue is appended to tsevqs on open(&amp;#34;/dev/ptpN&amp;#34;) and
removed and freed on close(), both under tsevqs_lock:&lt;/p&gt;
&lt;p&gt;scoped_guard(spinlock_irq, &amp;amp;ptp-&amp;gt;tsevqs_lock)
		list_del(&amp;amp;queue-&amp;gt;qlist);
	bitmap_free(queue-&amp;gt;mask);
	kfree(queue);&lt;/p&gt;
&lt;p&gt;So a read of /sys/class/ptp/ptpN/fifo running concurrently with a
close() of a /dev/ptpN fd can have list_count_nodes() walk into the
queue that close() is removing and freeing, dereferencing freed memory
(use-after-free) or a poisoned list pointer.&lt;/p&gt;
&lt;p&gt;Take tsevqs_lock around the list walk. The fifo only ever draws from the
first queue, which is the registration-time queue created in
ptp_clock_register() and freed only in ptp_clock_release(); that cannot
run while the sysfs attribute is being read, so the dequeue from
queue-&amp;gt;buf under queue-&amp;gt;lock may stay outside tsevqs_lock and the lock
order is unchanged.&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;ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked&lt;/p&gt;
&lt;p&gt;extts_fifo_show() walks ptp-&amp;gt;tsevqs with list_count_nodes() and then
list_first_entry() without holding ptp-&amp;gt;tsevqs_lock, the spinlock that
&amp;#34;protects tsevqs from concurrent access&amp;#34;. Every other accessor of the
list honours it: ptp_open() (list_add_tail), ptp_release() (list_del
followed by kfree of the per-fd queue), ptp_clock_release() and
ptp_clock_event() all take tsevqs_lock. extts_fifo_show() is the only
one that does not.&lt;/p&gt;
&lt;p&gt;A per-fd timestamp queue is appended to tsevqs on open(&amp;#34;/dev/ptpN&amp;#34;) and
removed and freed on close(), both under tsevqs_lock:&lt;/p&gt;
&lt;p&gt;scoped_guard(spinlock_irq, &amp;amp;ptp-&amp;gt;tsevqs_lock)
		list_del(&amp;amp;queue-&amp;gt;qlist);
	bitmap_free(queue-&amp;gt;mask);
	kfree(queue);&lt;/p&gt;
&lt;p&gt;So a read of /sys/class/ptp/ptpN/fifo running concurrently with a
close() of a /dev/ptpN fd can have list_count_nodes() walk into the
queue that close() is removing and freeing, dereferencing freed memory
(use-after-free) or a poisoned list pointer.&lt;/p&gt;
&lt;p&gt;Take tsevqs_lock around the list walk. The fifo only ever draws from the
first queue, which is the registration-time queue created in
ptp_clock_register() and freed only in ptp_clock_release(); that cannot
run while the sysfs attribute is being read, so the dequeue from
queue-&amp;gt;buf under queue-&amp;gt;lock may stay outside tsevqs_lock and the lock
order is unchanged.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99755</guid>
    </item>
    <item>
      <title>GHSA-6923-mrgg-7fjf</title>
      <link>https://db.gcve.eu/vuln/ghsa-6923-mrgg-7fjf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked&lt;/p&gt;
&lt;p&gt;extts_fifo_show() walks ptp-&amp;gt;tsevqs with list_count_nodes() and then
list_first_entry() without holding ptp-&amp;gt;tsevqs_lock, the spinlock that
&amp;#34;protects tsevqs from concurrent access&amp;#34;. Every other accessor of the
list honours it: ptp_open() (list_add_tail), ptp_release() (list_del
followed by kfree of the per-fd queue), ptp_clock_release() and
ptp_clock_event() all take tsevqs_lock. extts_fifo_show() is the only
one that does not.&lt;/p&gt;
&lt;p&gt;A per-fd timestamp queue is appended to tsevqs on open(&amp;#34;/dev/ptpN&amp;#34;) and
removed and freed on close(), both under tsevqs_lock:&lt;/p&gt;
&lt;p&gt;scoped_guard(spinlock_irq, &amp;amp;ptp-&amp;gt;tsevqs_lock)
		list_del(&amp;amp;queue-&amp;gt;qlist);
	bitmap_free(queue-&amp;gt;mask);
	kfree(queue);&lt;/p&gt;
&lt;p&gt;So a read of /sys/class/ptp/ptpN/fifo running concurrently with a
close() of a /dev/ptpN fd can have list_count_nodes() walk into the
queue that close() is removing and freeing, dereferencing freed memory
(use-after-free) or a poisoned list pointer.&lt;/p&gt;
&lt;p&gt;Take tsevqs_lock around the list walk. The fifo only ever draws from the
first queue, which is the registration-time queue created in
ptp_clock_register() and freed only in ptp_clock_release(); that cannot
run while the sysfs attribute is being read, so the dequeue from
queue-&amp;gt;buf under queue-&amp;gt;lock may stay outside tsevqs_lock and the lock
order is unchanged.&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;ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked&lt;/p&gt;
&lt;p&gt;extts_fifo_show() walks ptp-&amp;gt;tsevqs with list_count_nodes() and then
list_first_entry() without holding ptp-&amp;gt;tsevqs_lock, the spinlock that
&amp;#34;protects tsevqs from concurrent access&amp;#34;. Every other accessor of the
list honours it: ptp_open() (list_add_tail), ptp_release() (list_del
followed by kfree of the per-fd queue), ptp_clock_release() and
ptp_clock_event() all take tsevqs_lock. extts_fifo_show() is the only
one that does not.&lt;/p&gt;
&lt;p&gt;A per-fd timestamp queue is appended to tsevqs on open(&amp;#34;/dev/ptpN&amp;#34;) and
removed and freed on close(), both under tsevqs_lock:&lt;/p&gt;
&lt;p&gt;scoped_guard(spinlock_irq, &amp;amp;ptp-&amp;gt;tsevqs_lock)
		list_del(&amp;amp;queue-&amp;gt;qlist);
	bitmap_free(queue-&amp;gt;mask);
	kfree(queue);&lt;/p&gt;
&lt;p&gt;So a read of /sys/class/ptp/ptpN/fifo running concurrently with a
close() of a /dev/ptpN fd can have list_count_nodes() walk into the
queue that close() is removing and freeing, dereferencing freed memory
(use-after-free) or a poisoned list pointer.&lt;/p&gt;
&lt;p&gt;Take tsevqs_lock around the list walk. The fifo only ever draws from the
first queue, which is the registration-time queue created in
ptp_clock_register() and freed only in ptp_clock_release(); that cannot
run while the sysfs attribute is being read, so the dequeue from
queue-&amp;gt;buf under queue-&amp;gt;lock may stay outside tsevqs_lock and the lock
order is unchanged.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-6923-mrgg-7fjf</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>
