<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 23:45:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80622 — char: tlclk: fix use-after-free in tlclk_cleanup()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80622</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;char: tlclk: fix use-after-free in tlclk_cleanup()&lt;/p&gt;
&lt;p&gt;This patch improves the module cleanup process in the tlclk driver to
prevent potential use-after-free and race conditions.&lt;/p&gt;
&lt;p&gt;Currently, the file_operations structure does not specify the .owner
field, which could allow the module to be unloaded while user-space
processes are still interacting with the device. Additionally, the
tlclk_cleanup() function frees the alarm_events memory before ensuring
that blocked processes in the waitqueue are fully awakened and that the
switchover_timer has completed.&lt;/p&gt;
&lt;p&gt;To address these cases, this patch:
- Sets &amp;#39;.owner = THIS_MODULE&amp;#39; in tlclk_fops to safely defer module
  unloading while the device is in use.
- Updates tlclk_cleanup() to explicitly wake up all blocked readers
  (wake_up_all), properly release hardware I/O regions, and safely
  delete the timer (timer_delete_sync) prior to freeing memory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;char: tlclk: fix use-after-free in tlclk_cleanup()&lt;/p&gt;
&lt;p&gt;This patch improves the module cleanup process in the tlclk driver to
prevent potential use-after-free and race conditions.&lt;/p&gt;
&lt;p&gt;Currently, the file_operations structure does not specify the .owner
field, which could allow the module to be unloaded while user-space
processes are still interacting with the device. Additionally, the
tlclk_cleanup() function frees the alarm_events memory before ensuring
that blocked processes in the waitqueue are fully awakened and that the
switchover_timer has completed.&lt;/p&gt;
&lt;p&gt;To address these cases, this patch:
- Sets &amp;#39;.owner = THIS_MODULE&amp;#39; in tlclk_fops to safely defer module
  unloading while the device is in use.
- Updates tlclk_cleanup() to explicitly wake up all blocked readers
  (wake_up_all), properly release hardware I/O regions, and safely
  delete the timer (timer_delete_sync) prior to freeing memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80622</guid>
    </item>
  </channel>
</rss>
