<?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>Mon, 28 Sep 2026 06:42:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-58094 — jfs: add check read-only before truncation in jfs_truncate_nolock()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-58094</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;jfs: add check read-only before truncation in jfs_truncate_nolock()&lt;/p&gt;
&lt;p&gt;Added a check for &amp;#34;read-only&amp;#34; mode in the `jfs_truncate_nolock`
function to avoid errors related to writing to a read-only
filesystem.&lt;/p&gt;
&lt;p&gt;Call stack:&lt;/p&gt;
&lt;p&gt;block_write_begin() {
  jfs_write_failed() {
    jfs_truncate() {
      jfs_truncate_nolock() {
        txEnd() {
          ...
          log = JFS_SBI(tblk-&amp;gt;sb)-&amp;gt;log;
          // (log == NULL)&lt;/p&gt;
&lt;p&gt;If the `isReadOnly(ip)` condition is triggered in
`jfs_truncate_nolock`, the function execution will stop, and no
further data modification will occur. Instead, the `xtTruncate`
function will be called with the &amp;#34;COMMIT_WMAP&amp;#34; flag, preventing
modifications in &amp;#34;read-only&amp;#34; mode.&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;jfs: add check read-only before truncation in jfs_truncate_nolock()&lt;/p&gt;
&lt;p&gt;Added a check for &amp;#34;read-only&amp;#34; mode in the `jfs_truncate_nolock`
function to avoid errors related to writing to a read-only
filesystem.&lt;/p&gt;
&lt;p&gt;Call stack:&lt;/p&gt;
&lt;p&gt;block_write_begin() {
  jfs_write_failed() {
    jfs_truncate() {
      jfs_truncate_nolock() {
        txEnd() {
          ...
          log = JFS_SBI(tblk-&amp;gt;sb)-&amp;gt;log;
          // (log == NULL)&lt;/p&gt;
&lt;p&gt;If the `isReadOnly(ip)` condition is triggered in
`jfs_truncate_nolock`, the function execution will stop, and no
further data modification will occur. Instead, the `xtTruncate`
function will be called with the &amp;#34;COMMIT_WMAP&amp;#34; flag, preventing
modifications in &amp;#34;read-only&amp;#34; mode.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-58094</guid>
    </item>
  </channel>
</rss>
