ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 4bf629262f9118ee91b1c3a518ebf2b3bcb22180, Kernel 79ed288cef201f1f212dfb934bcaac75572fb8f6, Kernel aeb974907642be095e38ecb1a400ca583958b2b0 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using ->NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.15, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <4bf629262f9118ee91b1c3a518ebf2b3bcb22180, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <79ed288cef201f1f212dfb934bcaac75572fb8f6, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <aeb974907642be095e38ecb1a400ca583958b2b0, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <f339d76a3a972601d0738b881b099d49ebbdc3a2 | 4bf629262f9118ee91b1c3a518ebf2b3bcb22180, 79ed288cef201f1f212dfb934bcaac75572fb8f6, aeb974907642be095e38ecb1a400ca583958b2b0, f339d76a3a972601d0738b881b099d49ebbdc3a2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket