<?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-29T13:38:02.673446+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-49493</id>
    <title>CVE-2022-49493 — ASoC: rt5645: Fix errorenous cleanup order</title>
    <updated>2026-09-29T13:38:02.690197+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>ASoC: rt5645: Fix errorenous cleanup order</p>
<p>There is a logic error when removing rt5645 device as the function
rt5645_i2c_remove() first cancel the &amp;rt5645-&gt;jack_detect_work and
delete the &amp;rt5645-&gt;btn_check_timer latter. However, since the timer
handler rt5645_btn_check_callback() will re-queue the jack_detect_work,
this cleanup order is buggy.</p>
<p>That is, once the del_timer_sync in rt5645_i2c_remove is concurrently
run with the rt5645_btn_check_callback, the canceled jack_detect_work
will be rescheduled again, leading to possible use-after-free.</p>
<p>This patch fix the issue by placing the del_timer_sync function before
the cancel_delayed_work_sync.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49493"/>
  </entry>
</feed>
