<?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-07T01:20:27.113956+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-53265</id>
    <title>CVE-2026-53265 — dm cache policy smq: check allocation under invalidate lock</title>
    <updated>2026-10-07T01:20:27.115457+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>dm cache policy smq: check allocation under invalidate lock</p>
<p>commit 2d1f7b65f5de ("dm cache policy smq: fix missing locks in
invalidating cache blocks") added mq-&gt;lock around the destructive part of
smq_invalidate_mapping(), but left the e-&gt;allocated check outside the
critical section.</p>
<p>That leaves a check-then-act race. Two concurrent invalidators can both
observe e-&gt;allocated as true before either of them takes mq-&gt;lock. The
first invalidator that acquires the lock removes the entry from the
queues and hash table and then calls free_entry(), which clears
e-&gt;allocated and puts the entry back on the free list. The second
invalidator can then acquire mq-&gt;lock and continue with the stale result
of the unlocked check.</p>
<p>This can corrupt the SMQ queues or hash table by deleting an entry that
is no longer on those structures. It can also hit the allocation check in
free_entry() when the same entry is freed again.</p>
<p>Move the allocation check under mq-&gt;lock so the predicate and the
destructive operations are serialized by the same lock.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-53265"/>
  </entry>
</feed>
