CVE-2026-80791: nvmet-auth: zero the AUTH_RECEIVE response buffer
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 1d6837d98bf966a041af65de5f78de7409ff83bc, 2dcc9226203da7275a9c29d20007da278d73d5e9, 3ddcfb013322aa37eaa7a0d344b73079c38dfa21.
Low priority for now. Upgrade to Linux Linux 1d6837d98bf966a041af65de5f78de7409ff83bc, 2dcc9226203da7275a9c29d20007da278d73d5e9, 3ddcfb013322aa37eaa7a0d344b73079c38dfa21 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.0affected
- db1312dd95488b5e6ff362ff66fcf953a46b1821 and later · before 447b668faa14710f611e714031e3739ac3ec3a4faffected · git
- db1312dd95488b5e6ff362ff66fcf953a46b1821 and later · before 8f6363c8d54dde95982f0ab45e77cf57ec0efd62affected · git
- db1312dd95488b5e6ff362ff66fcf953a46b1821 and later · before dfcf013f77709ebdb282767edc2795a37cab5b57affected · git
- db1312dd95488b5e6ff362ff66fcf953a46b1821 and later · before b26189d28442183a8b5edb754f4a6918f77ca84eaffected · git
- db1312dd95488b5e6ff362ff66fcf953a46b1821 and later · before 2dcc9226203da7275a9c29d20007da278d73d5e9affected · git
- db1312dd95488b5e6ff362ff66fcf953a46b1821 and later · before 1d6837d98bf966a041af65de5f78de7409ff83bcaffected · git
- db1312dd95488b5e6ff362ff66fcf953a46b1821 and later · before 3ddcfb013322aa37eaa7a0d344b73079c38dfa21affected · git
- before 6.0not affected · semver
- 6.1.185 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.107-1 | 6.12.107-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80789Sep 4, 2026 · nvmet-tcp: bound SGL data length before allocating command buffers0Monitor
- ← EarlierCVE-2026-80790Sep 4, 2026 · nvmet-fc: fix invalid free in LS IOD error path0Monitor
- Later →CVE-2026-80792Sep 4, 2026 · ipv6: fix use-after-free in ip6_finish_output2()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1d6837d98bf966a041af65de5f78de7409ff83bc | Vendor (CNA) |
| Linux Linux | 2dcc9226203da7275a9c29d20007da278d73d5e9 | Vendor (CNA) |
| Linux Linux | 3ddcfb013322aa37eaa7a0d344b73079c38dfa21 | Vendor (CNA) |
| Linux Linux | 447b668faa14710f611e714031e3739ac3ec3a4f | Vendor (CNA) |
| Linux Linux | 8f6363c8d54dde95982f0ab45e77cf57ec0efd62 | Vendor (CNA) |
| Linux Linux | b26189d28442183a8b5edb754f4a6918f77ca84e | Vendor (CNA) |
| Linux Linux | dfcf013f77709ebdb282767edc2795a37cab5b57 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/2dcc9226203da7275a9c29d20007da278d73d5e9
- git.kernel.org/stable/c/3ddcfb013322aa37eaa7a0d344b73079c38dfa21
- git.kernel.org/stable/c/447b668faa14710f611e714031e3739ac3ec3a4f
- git.kernel.org/stable/c/8f6363c8d54dde95982f0ab45e77cf57ec0efd62
- git.kernel.org/stable/c/b26189d28442183a8b5edb754f4a6918f77ca84e
- git.kernel.org/stable/c/dfcf013f77709ebdb282767edc2795a37cab5b57
Vendor advisories and official records. Exploit/PoC links are deliberately left out.