<?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:03:23.920000+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-99485</id>
    <title>fkie_cve-2026-99485</title>
    <updated>2026-11-20T21:03:23.927762+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>accel/amdxdna: clear the mailbox channel pointer when starting it fails</p>
<p>aie2_create_context() allocates a mailbox channel, starts it, and on a
failed start frees it again:</p>
<p>hwctx-&gt;priv-&gt;mbox_chann = xdna_mailbox_alloc_channel(ndev-&gt;mbox);
	...
	ret = xdna_mailbox_start_channel(hwctx-&gt;priv-&gt;mbox_chann, ...);
	if (ret)
		goto free_channel;
	...
free_channel:
	xdna_mailbox_free_channel(hwctx-&gt;priv-&gt;mbox_chann);</p>
<p>hwctx-&gt;priv-&gt;mbox_chann keeps pointing at the freed channel. That
pointer is the driver's own test for whether a hardware context has a
usable channel: aie2_destroy_context() returns early on NULL,
aie2_sched_job_run() refuses to run a job on NULL, and the message
helpers return -ENODEV on NULL. A stale pointer passes all of them.</p>
<p>It matters on the restart path. aie2_hwctx_restart() calls
aie2_create_context() again on a hardware context that is already live,
after aie2_hwctx_stop() has torn its channel down, and the context
survives a failure there: aie2_sched_job_timedout() discards the return
value entirely, and aie2_hwctx_resume() only propagates it. What is
left is a live hardware context holding a freed channel, and every
later user of it takes the non-NULL branch:</p>
<p>- the next job submitted reaches xdna_mailbox_send_msg() on the freed
    channel, via the !mbox_chann guard in aie2_sched_job_run(),
  - a second command timeout reaches aie2_hwctx_stop() -&gt;
    aie2_destroy_context(),
  - closi…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99485"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-2255-vxmv-hcqm</id>
    <title>GHSA-2255-vxmv-hcqm</title>
    <updated>2026-11-20T21:03:23.927972+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>accel/amdxdna: clear the mailbox channel pointer when starting it fails</p>
<p>aie2_create_context() allocates a mailbox channel, starts it, and on a
failed start frees it again:</p>
<p>hwctx-&gt;priv-&gt;mbox_chann = xdna_mailbox_alloc_channel(ndev-&gt;mbox);
	...
	ret = xdna_mailbox_start_channel(hwctx-&gt;priv-&gt;mbox_chann, ...);
	if (ret)
		goto free_channel;
	...
free_channel:
	xdna_mailbox_free_channel(hwctx-&gt;priv-&gt;mbox_chann);</p>
<p>hwctx-&gt;priv-&gt;mbox_chann keeps pointing at the freed channel. That
pointer is the driver's own test for whether a hardware context has a
usable channel: aie2_destroy_context() returns early on NULL,
aie2_sched_job_run() refuses to run a job on NULL, and the message
helpers return -ENODEV on NULL. A stale pointer passes all of them.</p>
<p>It matters on the restart path. aie2_hwctx_restart() calls
aie2_create_context() again on a hardware context that is already live,
after aie2_hwctx_stop() has torn its channel down, and the context
survives a failure there: aie2_sched_job_timedout() discards the return
value entirely, and aie2_hwctx_resume() only propagates it. What is
left is a live hardware context holding a freed channel, and every
later user of it takes the non-NULL branch:</p>
<p>- the next job submitted reaches xdna_mailbox_send_msg() on the freed
    channel, via the !mbox_chann guard in aie2_sched_job_run(),
  - a second command timeout reaches aie2_hwctx_stop() -&gt;
    aie2_destroy_context(),
  - closi…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-2255-vxmv-hcqm"/>
  </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:03:23.928036+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>
