<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T20:14:02.926369+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2026-89592</id>
    <title>CVE-2026-89592 — accel/rocket: fix NULL dereference and integer overflow in rocket_job_push()</title>
    <updated>2026-10-07T20:14:02.946671+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>accel/rocket: fix NULL dereference and integer overflow in rocket_job_push()</p>
<p>rocket_job_push() allocates a temporary array to hold all input and
output GEM object pointers:</p>
<p>bos = kvmalloc_array(job-&gt;in_bo_count + job-&gt;out_bo_count,
                         sizeof(void *), GFP_KERNEL);
    memcpy(bos, job-&gt;in_bos, job-&gt;in_bo_count * sizeof(void *));
    memcpy(&amp;bos[job-&gt;in_bo_count], job-&gt;out_bos, ...);</p>
<p>Two bugs exist:</p>
<p>1. Missing NULL check: if kvmalloc_array() fails, bos is NULL and
   the subsequent memcpy() dereferences it, causing a kernel NULL
   pointer dereference.</p>
<p>2. Integer overflow: in_bo_count and out_bo_count are both u32, set
   directly from userspace-supplied in_bo_handle_count and
   out_bo_handle_count with no prior validation. Their sum is computed
   in u32 arithmetic and can wrap to a smaller value, causing the
   allocation count passed to kvmalloc_array() to be smaller than
   intended. Subsequent uses still operate on the original counts when
   copying and locking objects, which may lead to out-of-bounds accesses
   on the temporary array.</p>
<p>Fix by using check_add_overflow() to detect count overflow before the
allocation, and adding a NULL check on the allocation result.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-89592"/>
  </entry>
</feed>
