<?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-28T23:50:18.031648+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-49954</id>
    <title>CVE-2022-49954 — Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag</title>
    <updated>2026-09-28T23:50:18.046007+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>Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag</p>
<p>syzbot is reporting hung task at __input_unregister_device() [1], for
iforce_close() waiting at wait_event_interruptible() with dev-&gt;mutex held
is blocking input_disconnect_device() from __input_unregister_device().</p>
<p>It seems that the cause is simply that commit c2b27ef672992a20 ("Input:
iforce - wait for command completion when closing the device") forgot to
call wake_up() after clear_bit().</p>
<p>Fix this problem by introducing a helper that calls clear_bit() followed
by wake_up_all().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49954"/>
  </entry>
</feed>
