smb/client: handle overlapping allocated ranges in fallocate
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2, Kernel 5.13, Kernel 5.14 and 14 more.
In the Linux kernel, the following vulnerability has been resolved: smb/client: handle overlapping allocated ranges in fallocate smb3_simple_fallocate_range() can skip holes when an allocated range returned by the server starts before the current fallocate offset. The skipped hole is not zero-filled, but fallocate still returns success. A later write to that hole may therefore fail with ENOSPC. The function queries allocated ranges so that it can preserve existing contents and write zeroes only into holes. However, the server may return a range that starts before the current fallocate offset. For example, assume the fallocate request is [100, 400) and the only allocated range returned by the server is [0, 200): Request: [100, 400) Server range: [ 0, 200) allocated Correct: [100, 200) allocated data, skip [200, 400) hole, zero-fill Current: [100, 300) skipped [300, 400) zero-filled afterwards The current code adds the full server range length, 200, to the current offset 100 and moves to 300. As a result, the hole in [200, 300) is skipped without being zero-filled. Fix this by advancing only over the part of the allocated range that overlaps the current fallocate offset. Ignore ranges that end before the current offset and reject ranges whose end offset overflows. This also prevents a malformed range length from causing an out-of-bounds zero-buffer read.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=c406bb9ece6ef63721daab106f132ff4b4234e81 <aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2, >=5.12.17 <5.13, >=5.13.2 <5.14, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <01719883235507b1585e4c51e320d9a7113dc698, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <377fe3e583e46369ee1004d5cfe12271d6589a68, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <437637f5ff3f573b2edf8571de91fb00a21eb4e6, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <7e08ab7a061b17ac1989a225c6afb53f44a86808, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <a4a09e5142835633fffbde68bd0a039ba4d4bf97, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <b09ae45d85dc816987a71db9eebc54b0ae288e94, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <f47c7277c03a636fcc3a57969f2dc09567b3c050, =2f9f4a2d0e6fcf0673ed51195e06e47abe966900, =5.14, =5e397c943424de94879830e72c95f2679e297a76, >=5.10.50 <5.10.265 | aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2, 5.13, 5.14, 01719883235507b1585e4c51e320d9a7113dc698, 377fe3e583e46369ee1004d5cfe12271d6589a68, 437637f5ff3f573b2edf8571de91fb00a21eb4e6, 7e08ab7a061b17ac1989a225c6afb53f44a86808, a4a09e5142835633fffbde68bd0a039ba4d4bf97, b09ae45d85dc816987a71db9eebc54b0ae288e94, f47c7277c03a636fcc3a57969f2dc09567b3c050, 5.10.265 |
| linux-kernel: Kernel | >=5.12.17 <5.13, >=5.13.2 <5.14, >=5.14.0 <5.15.216, >=5.16.0 <6.1.183, >=6.13.0 <6.18.42, >=6.19.0 <7.1.6, >=6.2.0 <6.6.148, >=6.7.0 <6.12.101, >=5.10.50 <5.10.265 | 5.13, 5.14, 5.15.216, 6.1.183, 6.18.42, 7.1.6, 6.6.148, 6.12.101, 5.10.265 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket