[CVE-2026-68388][MODERATE 7.0] smb/client: handle overlapping allocated ranges in fallocate [ Upstream

[CVE-2026-68388][MODERATE 7.0] smb/client: handle overlapping allocated ranges in fallocate [ Upstream

[AL-KERNEL]

CVE: CVE-2026-68388
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: smb/client: handle overlapping allocated ranges in fallocate [ Upstream
Commit: 437637f5ff3f573b2edf8571de91fb00a21eb4e6
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=437637f5ff3f573b2edf8571de91fb00a21eb4e6
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68388
Analysis date: Mon, 10 Aug 2026 19:32:31 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: NO

Summary:
A malicious SMB server can return overlapping or malformed allocated ranges that cause SMB client fallocate emulation to skip zero filling and may trigger a constrained out-of-bounds zero-buffer read, leading mainly to storage operation failure and limited confidentiality concern.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68388 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68388

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-68388	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:H';CWE-125;*CWE-20;CWE-682;CWE-754;Other CVSS 'AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L';BEST CVSS score: '5.9';DESCR 'SMB client fallocate emulation can mishandle allocated ranges returned by the server when a returned range starts before the current fallocate offset. This can skip a hole without zero filling it, while fallocate still reports success, and a later write to that hole may fail with ENOSPC. A malformed range length can also lead to an out of bounds read from the zero buffer during the client side zero write path. For the CVSS the PR:N is used because the attacker can be a malicious or compromised SMB server and does not need local privileges on the victim client. UI:R is used because the victim normally has to mount or use the SMB share and trigger a fallocate operation. The issue is network reachable from the SMB server side, but in practice SMB shares are often deployed inside trusted enterprise or storage networks rather than exposed to the public Internet. Impact is mainly denial of service and limited confidentiality risk from an out of bounds read, with no clear privilege escalation or arbitrary write primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	WRITE OOB DISK SERVERTOCLIENT KPANIC 	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=5
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Triggered signals:

* Remote reachable / network-triggerable: +2
  The attacker can plausibly be a malicious or compromised SMB server returning crafted allocated range metadata to the Linux SMB client.

* Confidentiality impact plausible: +1
  The commit explicitly says the fix prevents a malformed range length from causing an out-of-bounds zero-buffer read. This is a limited read primitive, not an arbitrary read, but it is enough for C:L concern.

* Availability impact realistic: +1
  Incorrect hole skipping can make fallocate return success while later writes fail with ENOSPC. The malformed range case may also cause abnormal client-side behavior.

* Important filesystem/storage path: +1
  This is in SMB client fallocate emulation and affects file allocation and zero-fill semantics for network filesystem storage.

Subtracting signals:

* Corruption primitive highly constrained or metadata-only: -1
  The OOB condition is described as a zero-buffer read, not OOB write, UAF, double free, type confusion, arbitrary write, or attacker-controlled kernel object corruption.

Not triggered:

* No strong LPE plausibility.
  There is no reclaim, stale callback, arbitrary write, page-cache corruption, refcount takeover, or controlled overwrite primitive shown.

* No generic strong memory corruption.
  The patch shows bounds correction and range validation, but not a strong corruption sink.

* No Dirty-Pipe-like primitive.
  There is no evidence of attacker-controlled writes into shared page-cache or COW-protected pages.

## 3. Reachability analysis

The most realistic attacker is a malicious or compromised SMB server. A victim client must mount or use the SMB share and trigger fallocate or an application path that performs equivalent allocation. This makes the issue network-influenced, but not a pure unauthenticated Internet-facing server-side bug.

Namespaces and containers do not materially lower the server-side requirement, but a local unprivileged user may help trigger the client operation if they can access the mounted SMB share. SMB client support is common in enterprise and storage environments, but mounted SMB shares are usually internal or trusted-network resources rather than public Internet exposure.

Call-site confidence: medium. The affected function and direct arithmetic are visible, but deeper behavior of smb3_simple_fallocate_write_range and the exact zero-buffer exposure path are not fully shown in the provided diff.

## 4. Severity interpretation

This behaves more like an actionable Moderate than an Important vulnerability. The strongest concrete issue is a server-influenced bounds and range-handling bug in a network filesystem client, with limited confidentiality concern from an OOB zero-buffer read and availability impact from incorrect allocation semantics.

The theoretical concern is that malformed server metadata affects kernel-side filesystem buffer handling. The realistic evidence does not show privilege escalation, arbitrary memory corruption, UAF, OOB write, or page-cache ownership bypass. Therefore the conservative score stays borderline, while the paranoid score reaches actionable Moderate because the issue is network-influenced and explicitly mentions an OOB read.

## 5. One-sentence report phrase

A malicious SMB server can return overlapping or malformed allocated ranges that cause SMB client fallocate emulation to skip zero filling and may trigger a constrained out-of-bounds zero-buffer read, leading mainly to storage operation failure and limited confidentiality concern.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the issue is network-influenced from the SMB server side and the commit explicitly mentions an out-of-bounds read, but the primitive appears constrained and there is no demonstrated LPE or arbitrary corruption path.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: smb/client: handle overlapping allocated ranges in fallocate [ Upstream
Commit: 437637f5ff3f573b2edf8571de91fb00a21eb4e6
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=437637f5ff3f573b2edf8571de91fb00a21eb4e6

Changed files:
  fs/smb/client/smb2ops.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=437637f5ff3f573b2edf8571de91fb00a21eb4e6

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68388 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68388

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L
  The Best / paranoid CVSS vector: AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:H
  The Best / paranoid CVSS score: 5.9

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 4
  Paranoid ActionableScore: 5

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).