<?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-30T00:11:46.259102+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-2025-22068</id>
    <title>CVE-2025-22068 — ublk: make sure ubq-&gt;canceling is set when queue is frozen</title>
    <updated>2026-09-30T00:11:46.421977+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>ublk: make sure ubq-&gt;canceling is set when queue is frozen</p>
<p>Now ublk driver depends on `ubq-&gt;canceling` for deciding if the request
can be dispatched via uring_cmd &amp; io_uring_cmd_complete_in_task().</p>
<p>Once ubq-&gt;canceling is set, the uring_cmd can be done via ublk_cancel_cmd()
and io_uring_cmd_done().</p>
<p>So set ubq-&gt;canceling when queue is frozen, this way makes sure that the
flag can be observed from ublk_queue_rq() reliably, and avoids
use-after-free on uring_cmd.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-22068"/>
  </entry>
</feed>
