nvme-fabrics: fix DHCHAP secret leak on parse failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f50fff73d620cd6e8f48bc58d4f1c944615a3fea · < afdee49a1b88ed9bb44e2b30e855297c169bcc53| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvme-fabrics: fix DHCHAP secret leak on parse failure
nvmf_parse_options() duplicates dhchap_secret and dhchap_ctrl_secret with match_strdup() before validating the DHHC-1: representation.
If validation fails, the parser returns -EINVAL before the temporary string in p is assigned to opts->dhchap_secret or opts->dhchap_ctrl_secret. nvmf_create_ctrl() subsequently frees opts, but nvmf_free_options() cannot release the unassigned temporary string. Each rejected option therefore leaks one allocation.
This is easy to miss because valid secrets transfer ownership to opts and are freed normally, while the malformed-secret path still returns the expected -EINVAL to userspace.
With CONFIG_NVME_HOST_AUTH enabled, the leak is reachable before the required-option checks and transport lookup. No NVMe-oF target or working transport connection is required; for example, repeatedly writing
dhchap_secret=BAD
or
From the CVE record · Linux
With CONFIG_NVME_HOST_AUTH enabled, the Linux kernel's nvme-fabrics option parser leaks an allocation when it rejects a malformed DHCHAP secret. A local attacker who can write repeatedly to /dev/nvme-fabrics can trigger the leak without an NVMe-oF target or working transport connection.
Operators running Linux kernels with CONFIG_NVME_HOST_AUTH enabled should check whether their kernel includes the fix.