Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80791nvmet-auth: zero the AUTH_RECEIVE response buffer

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 447b668faa14710f611e714031e3739ac3ec3a4f
    • affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 8f6363c8d54dde95982f0ab45e77cf57ec0efd62
    • affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < dfcf013f77709ebdb282767edc2795a37cab5b57
    • affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < b26189d28442183a8b5edb754f4a6918f77ca84e
    • affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 2dcc9226203da7275a9c29d20007da278d73d5e9
    • affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 1d6837d98bf966a041af65de5f78de7409ff83bc
    • affected db1312dd95488b5e6ff362ff66fcf953a46b1821 – < 3ddcfb013322aa37eaa7a0d344b73079c38dfa21
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.154 – ≤ 6.6.*
    • unaffected 6.12.106 – ≤ 6.12.*
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80791 badge
[![CVE-2026-80791](https://cveledger.app/badge/CVE-2026-80791.svg)](https://cveledger.app/cve/CVE-2026-80791)

Record last updated .