<?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-24T16:58:27.874903+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-98973</id>
    <title>fkie_cve-2026-98973</title>
    <updated>2026-10-24T16:58:27.885501+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>drm/bridge: Fix unlocked list_del in drm_bridge_add()</p>
<p>When re-adding a bridge that was previously removed, drm_bridge_add()
drops it from bridge_lingering_list without holding bridge_lock.</p>
<p>Both bridge_list and bridge_lingering_list are protected by bridge_lock,
as they are concurrently modified by drm_bridge_remove() and
__drm_bridge_free(), and walked by the debugfs 'bridges' file.  Running
the list_empty() test and the list_del_init() outside of the lock may
therefore corrupt either list.</p>
<p>Perform both under bridge_lock.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-98973"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-69cp-rcr3-v67w</id>
    <title>GHSA-69cp-rcr3-v67w</title>
    <updated>2026-10-24T16:58:27.885602+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>drm/bridge: Fix unlocked list_del in drm_bridge_add()</p>
<p>When re-adding a bridge that was previously removed, drm_bridge_add()
drops it from bridge_lingering_list without holding bridge_lock.</p>
<p>Both bridge_list and bridge_lingering_list are protected by bridge_lock,
as they are concurrently modified by drm_bridge_remove() and
__drm_bridge_free(), and walked by the debugfs 'bridges' file.  Running
the list_empty() test and the list_del_init() outside of the lock may
therefore corrupt either list.</p>
<p>Perform both under bridge_lock.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-69cp-rcr3-v67w"/>
  </entry>
</feed>
