<?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-29T15:15:41.151651+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-2023-52983</id>
    <title>CVE-2023-52983 — block, bfq: fix uaf for bfqq in bic_set_bfqq()</title>
    <updated>2026-09-29T15:15:41.699734+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>block, bfq: fix uaf for bfqq in bic_set_bfqq()</p>
<p>After commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq-&gt;bic'"),
bic-&gt;bfqq will be accessed in bic_set_bfqq(), however, in some context
bic-&gt;bfqq will be freed, and bic_set_bfqq() is called with the freed
bic-&gt;bfqq.</p>
<p>Fix the problem by always freeing bfqq after bic_set_bfqq().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-52983"/>
  </entry>
</feed>
