<?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-10-01T20:00:45.937850+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-2022-50329</id>
    <title>CVE-2022-50329 — block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq</title>
    <updated>2026-10-01T20:00:46.274674+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 bfq_exit_icq_bfqq</p>
<p>Commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq-&gt;bic'")
will access 'bic-&gt;bfqq' in bic_set_bfqq(), however, bfq_exit_icq_bfqq()
can free bfqq first, and then call bic_set_bfqq(), which will cause uaf.</p>
<p>Fix the problem by moving bfq_exit_bfqq() behind bic_set_bfqq().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-50329"/>
  </entry>
</feed>
