smb: client: fix use-before-check of ReparseDataLength in reparse_buf_ptr()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 6.6.160, Kernel 711cf71300d7992f450600df8864917d3538679f, Kernel b70bc592afd19732e2e4563300ebe8f974280365 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-before-check of ReparseDataLength in reparse_buf_ptr() reparse_buf_ptr() reads buf->ReparseDataLength before checking that count covers the full fixed header: buf = (struct reparse_data_buffer *)((u8 *)io + off); len = sizeof(*buf); /* 8 bytes */ rdlen = le16_to_cpu(buf->ReparseDataLength); /* offset 4, 2 bytes */ if (count < len || count < rdlen + len) /* check comes after */ struct reparse_data_buffer has ReparseDataLength at offset 4. If a server returns OutputCount < 6, the read at offset 4-5 reaches past the end of the received data. The off+count bounds against iov_len were already validated, but that does not protect against count being smaller than sizeof(*buf). Split the check: verify count >= sizeof(*buf) before reading ReparseDataLength, then verify count covers the data region.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=6.6.32 <6.6.160, >=67ec9949b0dfe78c99e110dd975eb7dc5645630c <711cf71300d7992f450600df8864917d3538679f, >=a158bb66b1373866d9fd5997565a58a573085539 <b70bc592afd19732e2e4563300ebe8f974280365, =6.8, >=67ec9949b0dfe78c99e110dd975eb7dc5645630c <05f78e6cf34ea3a285053bd5999e08e8ac298bd5 | 6.6.160, 711cf71300d7992f450600df8864917d3538679f, b70bc592afd19732e2e4563300ebe8f974280365, 05f78e6cf34ea3a285053bd5999e08e8ac298bd5 |
| linux-kernel: Kernel | >=6.8.0 <7.2.4, >=6.6.32 <6.6.160 | 7.2.4, 6.6.160 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket