Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-68388

smb/client: handle overlapping allocated ranges in fallocate

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.265, 5.13, 5.14, 5.15.216, 6.1.183, and 4 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From c406bb9ece6ef63721daab106f132ff4b4234e81 · fixed in aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2; From 966a3cb7c7db786452a87afdc3b48858fc4d4d6b · fixed in 01719883235507b1585e4c51e320d9a7113dc698; From 966a3cb7c7db786452a87afdc3b48858fc4d4d6b · fixed in f47c7277c03a636fcc3a57969f2dc09567b3c050; From 966a3cb7c7db786452a87afdc3b48858fc4d4d6b · fixed in 437637f5ff3f573b2edf8571de91fb00a21eb4e6; From 966a3cb7c7db786452a87afdc3b48858fc4d4d6b · fixed in 377fe3e583e46369ee1004d5cfe12271d6589a68; From 966a3cb7c7db786452a87afdc3b48858fc4d4d6b · fixed in 7e08ab7a061b17ac1989a225c6afb53f44a86808; From 966a3cb7c7db786452a87afdc3b48858fc4d4d6b · fixed in a4a09e5142835633fffbde68bd0a039ba4d4bf97; From 966a3cb7c7db786452a87afdc3b48858fc4d4d6b · fixed in b09ae45d85dc816987a71db9eebc54b0ae288e94; From 5.10.50 · fixed in 5.10.265; From 5.12.17 · fixed in 5.13; From 5.13.2 · fixed in 5.14

  • Linux Linux

    5.14

  • KernelLinux

    fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.14.0 · fixed in 6.1.183; From 5.16.0 · fixed in 6.6.148; From 6.2.0 · fixed in 6.12.101; From 6.7.0 · fixed in 6.18.42; From 6.13.0 · fixed in 7.1.6

References 8

git.kernel.org