<?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-11-20T21:04:47.664827+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/fkie_cve-2026-99755</id>
    <title>fkie_cve-2026-99755</title>
    <updated>2026-11-20T21:04:47.668820+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked</p>
<p>extts_fifo_show() walks ptp-&gt;tsevqs with list_count_nodes() and then
list_first_entry() without holding ptp-&gt;tsevqs_lock, the spinlock that
"protects tsevqs from concurrent access". 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.</p>
<p>A per-fd timestamp queue is appended to tsevqs on open("/dev/ptpN") and
removed and freed on close(), both under tsevqs_lock:</p>
<p>scoped_guard(spinlock_irq, &amp;ptp-&gt;tsevqs_lock)
		list_del(&amp;queue-&gt;qlist);
	bitmap_free(queue-&gt;mask);
	kfree(queue);</p>
<p>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.</p>
<p>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-&gt;buf under queue-&gt;lock may stay outside tsevqs_lock and the lock
order is unchanged.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99755"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-6923-mrgg-7fjf</id>
    <title>GHSA-6923-mrgg-7fjf</title>
    <updated>2026-11-20T21:04:47.668893+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked</p>
<p>extts_fifo_show() walks ptp-&gt;tsevqs with list_count_nodes() and then
list_first_entry() without holding ptp-&gt;tsevqs_lock, the spinlock that
"protects tsevqs from concurrent access". 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.</p>
<p>A per-fd timestamp queue is appended to tsevqs on open("/dev/ptpN") and
removed and freed on close(), both under tsevqs_lock:</p>
<p>scoped_guard(spinlock_irq, &amp;ptp-&gt;tsevqs_lock)
		list_del(&amp;queue-&gt;qlist);
	bitmap_free(queue-&gt;mask);
	kfree(queue);</p>
<p>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.</p>
<p>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-&gt;buf under queue-&gt;lock may stay outside tsevqs_lock and the lock
order is unchanged.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-6923-mrgg-7fjf"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</id>
    <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T21:04:47.668924+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4695"/>
  </entry>
</feed>
