https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 23:47:34 +0000 https://vulnerability.circl.lu/vuln/cve-2025-39819 <p><strong>Affected:</strong> Linux, Siemens SIMATIC CN 4100</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fs/smb: Fix inconsistent refcnt update</p> <p>A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks.</p> <p>Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned.</p> <p>To fix the bug, an extra goto label &#34;out&#34; is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label &#34;finished&#34; and &#34;out&#34; can be safely ignored. According to the definition of function `is_replayable_error`, the error code of &#34;-ENOMEM&#34; is not recoverable. Therefore, the replay logic also gets ignored.</p> <p><strong>Affected:</strong> Linux, Siemens SIMATIC CN 4100</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fs/smb: Fix inconsistent refcnt update</p> <p>A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks.</p> <p>Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned.</p> <p>To fix the bug, an extra goto label &#34;out&#34; is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label &#34;finished&#34; and &#34;out&#34; can be safely ignored. According to the definition of function `is_replayable_error`, the error code of &#34;-ENOMEM&#34; is not recoverable. Therefore, the replay logic also gets ignored.</p> https://vulnerability.circl.lu/vuln/cve-2025-39819