<?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-29T08:50:09.627965+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-2026-89831</id>
    <title>CVE-2026-89831 — f2fs: protect critical_task_priority updates with s_umount</title>
    <updated>2026-09-29T08:50:09.631022+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>f2fs: protect critical_task_priority updates with s_umount</p>
<p>The sysfs store path already takes s_umount for GC thread control
entries, and ckpt_thread_ioprio is covered as well.</p>
<p>critical_task_priority also updates checkpoint or GC kthread scheduling
state, but it is not covered by that serialization. It can race with
remount or teardown paths that are stopping those threads.</p>
<p>Protect critical_task_priority sysfs writes with s_umount too.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89831"/>
  </entry>
</feed>
