CVE-2026-68388
Linux kernel vulnerability
- Published10 Aug 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/01719883235507b1585e4c51e320d9a7113dc698
- https://git.kernel.org/stable/c/377fe3e583e46369ee1004d5cfe12271d6589a68
- https://git.kernel.org/stable/c/437637f5ff3f573b2edf8571de91fb00a21eb4e6
- https://git.kernel.org/stable/c/7e08ab7a061b17ac1989a225c6afb53f44a86808
- https://git.kernel.org/stable/c/a4a09e5142835633fffbde68bd0a039ba4d4bf97
- https://git.kernel.org/stable/c/aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2
- https://git.kernel.org/stable/c/b09ae45d85dc816987a71db9eebc54b0ae288e94
- https://git.kernel.org/stable/c/f47c7277c03a636fcc3a57969f2dc09567b3c050
Frequently asked
Is CVE-2026-68388 being actively exploited?
CVE-2026-68388 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.51%.
How severe is CVE-2026-68388?
CVE-2026-68388 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.51% probability of exploitation.
How do I fix CVE-2026-68388?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-68388 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.