CVE-2026-64319nvmet-auth: validate reply message payload bounds against transfer length
- 9.1CriticalCVSS base score
- 0.56%Exploitation in 30 daysEPSS · top 53% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: validate reply message payload bounds against transfer length nvmet_auth_reply() accesses the variable-length rval[] array using attacker-controlled hl (hash length) and dhvlen (DH value length) fields without verifying they fit within the allocated buffer of tl bytes. A malicious NVMe-oF initiator can craft a DHCHAP_REPLY message with a small transfer length but large hl/dhvlen values, causing out-of-bounds heap reads when the target processes the DH public key (rval + 2*hl) or performs the host response memcmp. With DH authentication configured, the OOB pointer is passed directly to sg_init_one() and read by crypto_kpp_compute_shared_secret(), reaching up to 526 bytes past the buffer. This is exploitable pre-authentication. Add bounds validation ensuring sizeof(*data) + 2*hl + dhvlen <= tl before any access to the variable-length fields. Discovered by Atuin - Automated Vulnerability Discovery Engine.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| NVDNVD · Modified | 3.1 | Critical9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.56% · top 53% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.1.
Affected products
- affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 04fb6ff8b87a0ffff3860ff52bdb2fd04b31ece5
- affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 80cd28b56ab62d3e7ed0a7bf05282e6d3ee5b2a0
- affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 999f6205ede984a786f35f727b01f971b98e215d
- affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 6d7649c1231dac14d906985d2936967e23041c26
- affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < caa71b3a43ea5c13fe7141cb019ebcb03b8ac857
- affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 3a413ece2504c70aa34a20be4dafec04e8c741f9
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/04fb6ff8b87a0ffff3860ff52bdb2fd04b31ece5 (opens in a new tab)
- https://git.kernel.org/stable/c/80cd28b56ab62d3e7ed0a7bf05282e6d3ee5b2a0 (opens in a new tab)
- https://git.kernel.org/stable/c/999f6205ede984a786f35f727b01f971b98e215d (opens in a new tab)
- https://git.kernel.org/stable/c/6d7649c1231dac14d906985d2936967e23041c26 (opens in a new tab)
- https://git.kernel.org/stable/c/caa71b3a43ea5c13fe7141cb019ebcb03b8ac857 (opens in a new tab)
- https://git.kernel.org/stable/c/3a413ece2504c70aa34a20be4dafec04e8c741f9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-49031 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64319)Record last updated .