Description
In the Linux kernel, the following vulnerability has been resolved:

nvmet-auth: reject short AUTH_RECEIVE buffers

nvmet_execute_auth_receive() trusts the AUTH_RECEIVE allocation length
after checking only that it is nonzero and matches the transfer length.
In the SUCCESS1 and FAILURE1/default states, that lets a remote NVMe-oF
initiator reach the fixed-size DH-HMAC-CHAP response builders with a
kmalloc() buffer shorter than the response, so nvmet_auth_success1() and
nvmet_auth_failure1() write past the allocation; both only WARN_ON the
short length and then format the message anyway.

Impact: A remote NVMe-oF initiator with access to an auth-enabled target
can trigger a 16-byte heap out-of-bounds write via a one-byte
AUTH_RECEIVE allocation length.

Compute the minimum response length for the current DH-HMAC-CHAP step in
nvmet_auth_receive_data_len() and report a zero data length when the
host-supplied allocation length is shorter, so the existing zero-length
check in nvmet_execute_auth_receive() rejects the command before any
builder runs. The SUCCESS1 minimum is sizeof(struct
nvmf_auth_dhchap_success1_data) plus the HMAC hash length, because the
response hash is written into the rval[] flexible-array tail, so the
minimum is state dependent rather than a flat sizeof. CHALLENGE keeps its
existing variable-length guard in nvmet_auth_challenge().

This is reachable only when in-band DH-HMAC-CHAP authentication is
configured on the target.
Published: 2026-08-15
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in the Linux kernel’s NVMe‑over‑Fabric authentication routine allows a remote initiator to send an AUTH_RECEIVE command whose allocation length is smaller than the size expected by the state machine. The code only verifies that the length is non‑zero and matches the transfer length, then writes the authentication response into a kmalloc buffer without ensuring it is large enough. This results in a 16‑byte heap out‑of-bounds write that corrupts kernel memory. The vulnerability can cause kernel crashes or, if an attacker controls the data written, lead to remote code execution. The outage or crash is triggered when the kernel reaches the fixed‑size DH‑HMAC‑CHAP response builders for the SUCCESS1 and FAILURE1 states.

Affected Systems

All Linux kernel releases that provide NVMe‑over‑Fabric support with DH‑HMAC‑CHAP authentication enabled and that have not incorporated the buffer‑length validation change are affected. In practice this includes any mainline kernel built with the nvmet_auth_* code prior to the remediation. Kernels that do not enable NVMe‑over‑Fabric, that run without the authentication subsystems, or that have been patched to reject short AUTH_RECEIVE buffers are not impacted. Kernels that do not serve NVMe‑over‑Fabric traffic to untrusted initiators or that have disabled authentication are also not impacted.

Risk and Exploitability

The flaw is remotely exploitable over the network by a well‑positioned NVMe‑oF initiator capable of issuing crafted AUTH_RECEIVE commands. EPSS score is <1%, and the vulnerability is not listed in the CISA KEV catalog, indicating that no large‑scale exploitation has been observed to date. Given the CVSS score of 9.8, the kernel‑space heap overflow is highly critical: it corrupts critical memory structures and can trigger system crashes or privilege escalation. In tightly controlled environments with trusted initiators the risk is lower, but in any scenario where the target is exposed to untrusted networks the potential for a severe denial‑of‑service or remote code execution event remains substantial. Thus, the vulnerability’s risk merits a high severity rating and immediate attention.

Generated by OpenCVE AI on August 18, 2026 at 02:11 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel release that includes the nvmet_auth buffer‑length validation fix
  • If the patch cannot be applied immediately, restrict the NVMe‑oF target to trusted initiators or disable DH‑HMAC‑CHAP authentication
  • Consider switching to an alternative authentication mechanism until the kernel is updated

Generated by OpenCVE AI on August 18, 2026 at 02:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4745-1 linux-6.12 security update
History

Tue, 18 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-787
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 17 Aug 2026 20:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-122

Mon, 17 Aug 2026 18:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-122

Mon, 17 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Sat, 15 Aug 2026 09:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-122

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: reject short AUTH_RECEIVE buffers nvmet_execute_auth_receive() trusts the AUTH_RECEIVE allocation length after checking only that it is nonzero and matches the transfer length. In the SUCCESS1 and FAILURE1/default states, that lets a remote NVMe-oF initiator reach the fixed-size DH-HMAC-CHAP response builders with a kmalloc() buffer shorter than the response, so nvmet_auth_success1() and nvmet_auth_failure1() write past the allocation; both only WARN_ON the short length and then format the message anyway. Impact: A remote NVMe-oF initiator with access to an auth-enabled target can trigger a 16-byte heap out-of-bounds write via a one-byte AUTH_RECEIVE allocation length. Compute the minimum response length for the current DH-HMAC-CHAP step in nvmet_auth_receive_data_len() and report a zero data length when the host-supplied allocation length is shorter, so the existing zero-length check in nvmet_execute_auth_receive() rejects the command before any builder runs. The SUCCESS1 minimum is sizeof(struct nvmf_auth_dhchap_success1_data) plus the HMAC hash length, because the response hash is written into the rval[] flexible-array tail, so the minimum is state dependent rather than a flat sizeof. CHALLENGE keeps its existing variable-length guard in nvmet_auth_challenge(). This is reachable only when in-band DH-HMAC-CHAP authentication is configured on the target.
Title nvmet-auth: reject short AUTH_RECEIVE buffers
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:40:42.219Z

Reserved: 2026-08-09T03:40:39.907Z

Link: CVE-2026-72130

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:21:30.453

Modified: 2026-08-17T06:18:12.680

Link: CVE-2026-72130

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-72130 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T02:15:04Z

Weaknesses