<?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-29T19:24:50.449500+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-40971</id>
    <title>CVE-2024-40971 — f2fs: remove clear SB_INLINECRYPT flag in default_options</title>
    <updated>2026-09-29T19:24:50.467001+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, Siemens RUGGEDCOM RST2428P, Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family, Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>f2fs: remove clear SB_INLINECRYPT flag in default_options</p>
<p>In f2fs_remount, SB_INLINECRYPT flag will be clear and re-set.
If create new file or open file during this gap, these files
will not use inlinecrypt. Worse case, it may lead to data
corruption if wrappedkey_v0 is enable.</p>
<p>Thread A:                               Thread B:</p>
<p>-f2fs_remount				-f2fs_file_open or f2fs_new_inode
  -default_options
	&lt;- clear SB_INLINECRYPT flag</p>
<p>-fscrypt_select_encryption_impl</p>
<p>-parse_options
	&lt;- set SB_INLINECRYPT again</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-40971"/>
  </entry>
</feed>
