https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 03:39:24 +0000 https://vulnerability.circl.lu/vuln/cve-2026-23220 <p><strong>Affected:</strong> Linux, Siemens RUGGEDCOM RST2428P</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix infinite loop caused by next_smb2_rcv_hdr_off reset in error paths</p> <p>The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() set work-&gt;next_smb2_rcv_hdr_off as zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header&#39;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with &#34;bad smb2 signature&#34; messages and high CPU usage.</p> <p>This patch fixes the issue by changing the return value from SERVER_HANDLER_CONTINUE to SERVER_HANDLER_ABORT. This ensures that the processing loop terminates immediately rather than attempting to continue from an invalidated offset.</p> <p><strong>Affected:</strong> Linux, Siemens RUGGEDCOM RST2428P</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix infinite loop caused by next_smb2_rcv_hdr_off reset in error paths</p> <p>The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() set work-&gt;next_smb2_rcv_hdr_off as zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header&#39;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with &#34;bad smb2 signature&#34; messages and high CPU usage.</p> <p>This patch fixes the issue by changing the return value from SERVER_HANDLER_CONTINUE to SERVER_HANDLER_ABORT. This ensures that the processing loop terminates immediately rather than attempting to continue from an invalidated offset.</p> https://vulnerability.circl.lu/vuln/cve-2026-23220