nvmet-auth: zero the AUTH_RECEIVE response buffer
Summary
| CVE | CVE-2026-80791 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-04 16:18:05 UTC |
| Updated | 2026-09-04 16:18:05 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: zero the AUTH_RECEIVE response buffer nvmet_execute_auth_receive() allocates the response buffer with kmalloc() sized by the host-supplied AUTH_RECEIVE allocation length, but the DH-HMAC-CHAP builders write only a fixed-size message into it. The full allocation length is then copied to the wire by nvmet_copy_to_sgl(), so a remote initiator receives the bytes past the built message -- up to nearly a page of uninitialized slab -- during the pre-authentication handshake. Allocate the buffer with kzalloc() so the unwritten tail is zeroed before it is sent; conforming responses are unaffected. |
Risk And Classification
EPSS: 0.002070000 probability, percentile 0.108030000 (date 2026-09-07)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected db1312dd95488b5e6ff362ff66fcf953a46b1821 447b668faa14710f611e714031e3739ac3ec3a4f git | Not specified |
| CNA | Linux | Linux | affected db1312dd95488b5e6ff362ff66fcf953a46b1821 8f6363c8d54dde95982f0ab45e77cf57ec0efd62 git | Not specified |
| CNA | Linux | Linux | affected db1312dd95488b5e6ff362ff66fcf953a46b1821 dfcf013f77709ebdb282767edc2795a37cab5b57 git | Not specified |
| CNA | Linux | Linux | affected db1312dd95488b5e6ff362ff66fcf953a46b1821 b26189d28442183a8b5edb754f4a6918f77ca84e git | Not specified |
| CNA | Linux | Linux | affected db1312dd95488b5e6ff362ff66fcf953a46b1821 2dcc9226203da7275a9c29d20007da278d73d5e9 git | Not specified |
| CNA | Linux | Linux | affected db1312dd95488b5e6ff362ff66fcf953a46b1821 1d6837d98bf966a041af65de5f78de7409ff83bc git | Not specified |
| CNA | Linux | Linux | affected db1312dd95488b5e6ff362ff66fcf953a46b1821 3ddcfb013322aa37eaa7a0d344b73079c38dfa21 git | Not specified |
| CNA | Linux | Linux | affected 6.0 | Not specified |
| CNA | Linux | Linux | unaffected 6.0 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.185 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.154 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.106 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.47 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.11 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.1 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/1d6837d98bf966a041af65de5f78de7409ff83bc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b26189d28442183a8b5edb754f4a6918f77ca84e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3ddcfb013322aa37eaa7a0d344b73079c38dfa21 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2dcc9226203da7275a9c29d20007da278d73d5e9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8f6363c8d54dde95982f0ab45e77cf57ec0efd62 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/dfcf013f77709ebdb282767edc2795a37cab5b57 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/447b668faa14710f611e714031e3739ac3ec3a4f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.