ksmbd: fix infinite loop caused by next_smb2_rcv_hdr_off reset in error paths
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f7b1c2f5642bbd60b1beef1f3298cbac81eb232c, Kernel 6.1.164, Kernel fb3b66bd72deb5543addaefa67963b34fb163a7b and 10 more.
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix infinite loop caused by next_smb2_rcv_hdr_off reset in error paths 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->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'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 "bad smb2 signature" messages and high CPU usage. 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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=be0f89d4419dc5413a1cf06db3671c9949be0d52 <f7b1c2f5642bbd60b1beef1f3298cbac81eb232c, >=6.1.71 <6.1.164, >=943cebf9ea3415ddefcd670d24d8883e97ba3d60 <fb3b66bd72deb5543addaefa67963b34fb163a7b, >=be0f89d4419dc5413a1cf06db3671c9949be0d52 <010eb01ce23b34b50531448b0da391c7f05a72af, >=be0f89d4419dc5413a1cf06db3671c9949be0d52 <5accdc5b7f28a81bbc5880ac0b8886e60c86e8c8, >=be0f89d4419dc5413a1cf06db3671c9949be0d52 <71b5e7c528315ca360a1825a4ad2f8ae48c5dc16, >=be0f89d4419dc5413a1cf06db3671c9949be0d52 <9135e791ec2709bcf0cda0335535c74762489498, =6.6, >=4b9b7ea1ffb1e34f01fa5726d0c184931b9ba565 <544adb0a6658ea1bff4064723761dbf05f95b1e2, >=5.15.145 <5.15.203 | f7b1c2f5642bbd60b1beef1f3298cbac81eb232c, 6.1.164, fb3b66bd72deb5543addaefa67963b34fb163a7b, 010eb01ce23b34b50531448b0da391c7f05a72af, 5accdc5b7f28a81bbc5880ac0b8886e60c86e8c8, 71b5e7c528315ca360a1825a4ad2f8ae48c5dc16, 9135e791ec2709bcf0cda0335535c74762489498, 544adb0a6658ea1bff4064723761dbf05f95b1e2, 5.15.203 |
| linux-kernel: Kernel | >=6.1.71 <6.1.164, >=6.13.0 <6.18.11, >=6.19.0 <6.19.1, >=6.6.0 <6.6.125, >=6.7.0 <6.12.72, >=5.15.145 <5.15.203 | 6.1.164, 6.18.11, 6.19.1, 6.6.125, 6.12.72, 5.15.203 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket