CVE-2026-68388: smb/client: handle overlapping allocated ranges in fallocate
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 01719883235507b1585e4c51e320d9a7113dc698, 377fe3e583e46369ee1004d5cfe12271d6589a68, 437637f5ff3f573b2edf8571de91fb00a21eb4e6; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 01719883235507b1585e4c51e320d9a7113dc698, 377fe3e583e46369ee1004d5cfe12271d6589a68, 437637f5ff3f573b2edf8571de91fb00a21eb4e6; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 10, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- CWE-125
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2f9f4a2d0e6fcf0673ed51195e06e47abe966900, 5e397c943424de94879830e72c95f2679e297a76, 5.14affected
- c406bb9ece6ef63721daab106f132ff4b4234e81 and later · before aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2affected · git
- 966a3cb7c7db786452a87afdc3b48858fc4d4d6b and later · before 01719883235507b1585e4c51e320d9a7113dc698affected · git
- 966a3cb7c7db786452a87afdc3b48858fc4d4d6b and later · before f47c7277c03a636fcc3a57969f2dc09567b3c050affected · git
- 966a3cb7c7db786452a87afdc3b48858fc4d4d6b and later · before 437637f5ff3f573b2edf8571de91fb00a21eb4e6affected · git
- 966a3cb7c7db786452a87afdc3b48858fc4d4d6b and later · before 377fe3e583e46369ee1004d5cfe12271d6589a68affected · git
- 966a3cb7c7db786452a87afdc3b48858fc4d4d6b and later · before 7e08ab7a061b17ac1989a225c6afb53f44a86808affected · git
- 966a3cb7c7db786452a87afdc3b48858fc4d4d6b and later · before a4a09e5142835633fffbde68bd0a039ba4d4bf97affected · git
- 966a3cb7c7db786452a87afdc3b48858fc4d4d6b and later · before b09ae45d85dc816987a71db9eebc54b0ae288e94affected · git
- 5.10.50 and later · before 5.10.265affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.157.1.el8_10 | 4.18.0-553.157.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.157.1.rt7.498.el8_10 | 4.18.0-553.157.1.rt7.498.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.157.1.rt7.498.el8_10 | 4.18.0-553.157.1.rt7.498.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.157.1.rt7.498.el8_10 | 4.18.0-553.157.1.rt7.498.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.157.1.rt7.498.el8_10 | 4.18.0-553.157.1.rt7.498.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.157.1.rt7.498.el8_10 | 4.18.0-553.157.1.rt7.498.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.157.1.rt7.498.el8_10 | 4.18.0-553.157.1.rt7.498.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.157.1.rt7.498.el8_10 | 4.18.0-553.157.1.rt7.498.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.157.1.rt7.498.el8_10 | 4.18.0-553.157.1.rt7.498.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.157.1.rt7.498.el8_10 | 4.18.0-553.157.1.rt7.498.el8_10 |
+66
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68384Aug 10, 2026 · drm/xe/vf: Fix VF CCS attach/detach race with in-flight BO moves31Monitor
- ← EarlierCVE-2026-68385Aug 10, 2026 · s390/checksum: Fix csum_partial() without vector facility39Monitor
- Later →CVE-2026-68391Aug 10, 2026 · Bluetooth: mgmt: hold reference for hci_conn in mgmt_pending_cmds31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01719883235507b1585e4c51e320d9a7113dc698 | Vendor (CNA) |
| Linux Linux | 377fe3e583e46369ee1004d5cfe12271d6589a68 | Vendor (CNA) |
| Linux Linux | 437637f5ff3f573b2edf8571de91fb00a21eb4e6 | Vendor (CNA) |
| Linux Linux | 5.10.265 | Vendor (CNA) |
| Linux Linux | 5.13 | Vendor (CNA) |
| Linux Linux | 5.14 | Vendor (CNA) |
| Linux Linux | 7e08ab7a061b17ac1989a225c6afb53f44a86808 | Vendor (CNA) |
| Linux Linux | a4a09e5142835633fffbde68bd0a039ba4d4bf97 | Vendor (CNA) |
| Linux Linux | aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2 | Vendor (CNA) |
| Linux Linux | b09ae45d85dc816987a71db9eebc54b0ae288e94 | Vendor (CNA) |
| Linux Linux | f47c7277c03a636fcc3a57969f2dc09567b3c050 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.157.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.157.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.157.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.157.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.157.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
+10
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-681600 days apartceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()39Monitor
- CVE-2026-680822 days apartlibceph: fix two unsafe bare decodes in decode_lockers()39Monitor
- CVE-2026-720845 days apartscsi: target: Bound PR-OUT TransportID parsing to the received buffer39Monitor
- CVE-2026-683430 days apartsmb: client: validate DFS referral PathConsumed36Monitor
- CVE-2026-6455114 days apartsctp: validate STALE_COOKIE cause length before reading staleness36Monitor
- CVE-2026-680980 days apartksmbd: bound DACL dedup walk to copied ACEs35Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/377fe3e583e46369ee1004d5cfe12271d6589a68
- git.kernel.org/stable/c/437637f5ff3f573b2edf8571de91fb00a21eb4e6
- git.kernel.org/stable/c/7e08ab7a061b17ac1989a225c6afb53f44a86808
- git.kernel.org/stable/c/a4a09e5142835633fffbde68bd0a039ba4d4bf97
- git.kernel.org/stable/c/aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2
- git.kernel.org/stable/c/b09ae45d85dc816987a71db9eebc54b0ae288e94
- git.kernel.org/stable/c/f47c7277c03a636fcc3a57969f2dc09567b3c050
Vendor advisories and official records. Exploit/PoC links are deliberately left out.