CVE-2026-80836: Linux kernel · crypto: virtio – bound the akcipher result length
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f77a956f6a19f9463ef1527c9d0cda50dded6b92 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 13:18 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f77a956f6a19f9463ef1527c9d0cda50dded6b92, e0ffee8adc71a0bc548e5ebc6e021c013a874d79, bd33cb19bcb432a4dd5e8f50be5e2547af1e9f78 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel after version 5.19. Users and administrators should update to a patched kernel version that includes the fix identified by the listed commits. No additional mitigation is required beyond applying the official patch.
Description
CVE-2026-80836 is a vulnerability in the Linux kernel's virtio crypto driver where the akcipher result length was not properly bounded, leading to an out-of-bounds read of kernel heap memory. The flaw occurs because the device-reported response length could exceed the allocated destination buffer size, causing sg_copy_from_buffer() to read beyond the intended memory region. The issue has been fixed by clamping the reported length to the originally requested destination length, ensuring no over-read occurs. This fix does not affect valid results from conforming devices.
References
- git.kernel.org/stable/c/e0ffee8adc71a0bc548e5ebc6e021c013a874d79 (opens in a new tab)
- git.kernel.org/stable/c/bd33cb19bcb432a4dd5e8f50be5e2547af1e9f78 (opens in a new tab)
- git.kernel.org/stable/c/12c4f29e97f31b013f77ad65ba7daeb02aaa6abe (opens in a new tab)
- git.kernel.org/stable/c/5545de5050cbc3594506d74f2c392b0716cf8bca (opens in a new tab)
- git.kernel.org/stable/c/3fda114a42f1510a4ec8a0b17a0cfc997952ccc2 (opens in a new tab)
- git.kernel.org/stable/c/1f9f877b1ef1fbd4ee95571cddf39c8002cee252 (opens in a new tab)
- git.kernel.org/stable/c/f77a956f6a19f9463ef1527c9d0cda50dded6b92 (opens in a new tab)