<?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-04T19:44:54.744759+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-2024-38583</id>
    <title>CVE-2024-38583 — nilfs2: fix use-after-free of timer for log writer thread</title>
    <updated>2026-10-04T19:44:54.747474+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>nilfs2: fix use-after-free of timer for log writer thread</p>
<p>Patch series "nilfs2: fix log writer related issues".</p>
<p>This bug fix series covers three nilfs2 log writer-related issues,
including a timer use-after-free issue and potential deadlock issue on
unmount, and a potential freeze issue in event synchronization found
during their analysis.  Details are described in each commit log.</p>
<p>This patch (of 3):</p>
<p>A use-after-free issue has been reported regarding the timer sc_timer on
the nilfs_sc_info structure.</p>
<p>The problem is that even though it is used to wake up a sleeping log
writer thread, sc_timer is not shut down until the nilfs_sc_info structure
is about to be freed, and is used regardless of the thread's lifetime.</p>
<p>Fix this issue by limiting the use of sc_timer only while the log writer
thread is alive.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-38583"/>
  </entry>
</feed>
