nvme-fabrics: fix DHCHAP secret leak on parse failure
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 15d7a35a489287109b5a7c157d53d9b8214f0318, Kernel 35ec48228f6739339583e5a73ca315156372e30d, Kernel 3ce0e9b43f355dfa0bdc0e0dd889795752285791 and 3 more.
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 dhchap_ctrl_secret=BAD to /dev/nvme-fabrics deterministically takes the leaking parse path. Free the temporary string before leaving both validation error paths. Use kfree_sensitive() because the copied option may contain secret material even when its representation is rejected, matching the sensitive cleanup used for stored DHCHAP secrets.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.0, >=f50fff73d620cd6e8f48bc58d4f1c944615a3fea <15d7a35a489287109b5a7c157d53d9b8214f0318, >=f50fff73d620cd6e8f48bc58d4f1c944615a3fea <35ec48228f6739339583e5a73ca315156372e30d, >=f50fff73d620cd6e8f48bc58d4f1c944615a3fea <3ce0e9b43f355dfa0bdc0e0dd889795752285791, >=f50fff73d620cd6e8f48bc58d4f1c944615a3fea <702c1ae0d31b44828ec3c87079def490c1ee1fb3, >=f50fff73d620cd6e8f48bc58d4f1c944615a3fea <afdee49a1b88ed9bb44e2b30e855297c169bcc53, >=f50fff73d620cd6e8f48bc58d4f1c944615a3fea <d21da6cc91ba1c4f1ae5ba007f3cb89e1c0c7549 | 15d7a35a489287109b5a7c157d53d9b8214f0318, 35ec48228f6739339583e5a73ca315156372e30d, 3ce0e9b43f355dfa0bdc0e0dd889795752285791, 702c1ae0d31b44828ec3c87079def490c1ee1fb3, afdee49a1b88ed9bb44e2b30e855297c169bcc53, d21da6cc91ba1c4f1ae5ba007f3cb89e1c0c7549 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket