<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T13:40:28.104716+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-68259</id>
    <title>CVE-2026-68259 — drm/amdkfd: Check bounds in allocate_event_notification_slot</title>
    <updated>2026-09-29T13:40:28.106956+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>drm/amdkfd: Check bounds in allocate_event_notification_slot</p>
<p>The valid event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT</p>
<p>allocate_event_notification_slot has an option to specify
an event id to allocate at, used by CRIU. We weren't checking
the bounds on that value.</p>
<p>Check them.</p>
<p>v2: Lower bounds check is unecessary because of idr_alloc
already rejecting negative numbers. Upper bounds check should
be KFD_SIGNAL_EVENT_LIMIT since the signal mode mappings might
not yet exist</p>
<p>(cherry picked from commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68259"/>
  </entry>
</feed>
