CVE-2026-80652: crypto: ccp - Treat zero-length cert chain as query for blob lengths
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.22% (FIRST EPSS).
- Fixed version: Linux Linux 13b4d5e055d344e34b864bced0a591ceaac7ad81, 1c587f30c6242cc37b3d6ee6d91daef84e51633f, 21650fe221ea9b72809140b691589dde8bff3eab.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 13b4d5e055d344e34b864bced0a591ceaac7ad81, 1c587f30c6242cc37b3d6ee6d91daef84e51633f, 21650fe221ea9b72809140b691589dde8bff3eab 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: crypto: ccp - Treat zero-length cert chain as query for blob lengths When handling a PDH export, treat a zero-length userspace cert chain buffer as a request to query the length of the relevant blobs. Failure to account for the zero-length buffer trips a BUG_ON() when running with CONFIG_DEBUG_VIRTUAL=y due to trying to get the physical address of the ZERO_SIZE_PTR (returned by kzalloc() on the bogus allocation). kernel BUG at arch/x86/mm/physaddr.c:28 ! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 30 UID: 0 PID: 28580 Comm: syz.2.18 Kdump: loaded Tainted: G W 6.18.16-smp-DEV #1 NONE Tainted: [W]=WARN Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025 RIP: 0010:__phys_addr+0x16a/0x180 arch/x86/mm/physaddr.c:28 RSP: 0018:ffffc9008329fc80 EFLAGS: 00010293 RAX: ffffffff8179110a RBX: 0000778000000010 RCX: ffff8884e6992600 RDX: 0000000000000000 RSI: 0000000080000010 RDI: 0000778000000010 RBP: ffffc9008329fdf0 R08: 0000000000000dc0 R09: 00000000ffffffff R10: dffffc0000000000 R11: fffffbfff126d297 R12: dffffc0000000000 R13: 1ffff92010653fc8 R14: 0000000080000010 R15: dffffc0000000000 FS: 0000555556bec9c0(0000) GS:ffff88aa4ce1c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fd3159e7000 CR3: 00000004fbc44000 CR4: 0000000000350ef0 Call Trace: <TASK> [<ffffffff853d3869>] sev_ioctl_do_pdh_export+0x559/0x7a0 drivers/crypto/ccp/sev-dev.c:2308 [<ffffffff853d1fdd>] sev_ioctl+0x2cd/0x480 drivers/crypto/ccp/sev-dev.c:2556 [<ffffffff82549ebc>] vfs_ioctl fs/ioctl.c:52 [inline] [<ffffffff82549ebc>] __do_sys_ioctl fs/ioctl.c:598 [inline] [<ffffffff82549ebc>] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:584 [<ffffffff8630115f>] do_syscall_x64 arch/x86/entry/syscall_64.c:64 [inline] [<ffffffff8630115f>] do_syscall_64+0x9f/0xf40 arch/x86/entry/syscall_64.c:98 [<ffffffff81000136>] entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fd3158eac39 </TASK> Thankfully, the bug is benign outside of CONFIG_DEBUG_VIRTUAL=y as getting the physical address is just arithmetic, and the PSP errors out before trying to write to the garbage address (which it must, otherwise querying the blob lengths would clobber memory at pfn=0).
- Published
- Aug 28, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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
- 4.16affected
- 76a2b524a4b1d6dc0f2421f9854a01d55d5e5436 and later · before 1c587f30c6242cc37b3d6ee6d91daef84e51633faffected · git
- 76a2b524a4b1d6dc0f2421f9854a01d55d5e5436 and later · before 13b4d5e055d344e34b864bced0a591ceaac7ad81affected · git
- 76a2b524a4b1d6dc0f2421f9854a01d55d5e5436 and later · before 94344bc7c9d70b04be718d841b92873aa3ea8191affected · git
- 76a2b524a4b1d6dc0f2421f9854a01d55d5e5436 and later · before 50c3c7df4f26d36b30bc950a7d780f7029fd52f8affected · git
- 76a2b524a4b1d6dc0f2421f9854a01d55d5e5436 and later · before ee717e73ab47253c82c134c342e32fcdfcfccd87affected · git
- 76a2b524a4b1d6dc0f2421f9854a01d55d5e5436 and later · before 21650fe221ea9b72809140b691589dde8bff3eabaffected · git
- 76a2b524a4b1d6dc0f2421f9854a01d55d5e5436 and later · before d88071a6ce091272726bedda26c105b85b23705faffected · git
- 76a2b524a4b1d6dc0f2421f9854a01d55d5e5436 and later · before ef8c9dacda2871accd64e3eda951fef6b788b1eaaffected · git
- before 4.16not 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-80646Aug 28, 2026 · ipv6: guard against possible NULL deref in __in6_dev_stats_get()30Monitor
- ← EarlierCVE-2026-80650Aug 28, 2026 · media: atomisp: gc2235: fix UAF and memory leak0Monitor
- Later →CVE-2026-80653Aug 28, 2026 · scsi: hisi_sas: Add slave_destroy interface for v3 hw33Monitor
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 | 13b4d5e055d344e34b864bced0a591ceaac7ad81 | Vendor (CNA) |
| Linux Linux | 1c587f30c6242cc37b3d6ee6d91daef84e51633f | Vendor (CNA) |
| Linux Linux | 21650fe221ea9b72809140b691589dde8bff3eab | Vendor (CNA) |
| Linux Linux | 50c3c7df4f26d36b30bc950a7d780f7029fd52f8 | Vendor (CNA) |
| Linux Linux | 94344bc7c9d70b04be718d841b92873aa3ea8191 | Vendor (CNA) |
| Linux Linux | d88071a6ce091272726bedda26c105b85b23705f | Vendor (CNA) |
| Linux Linux | ee717e73ab47253c82c134c342e32fcdfcfccd87 | Vendor (CNA) |
| Linux Linux | ef8c9dacda2871accd64e3eda951fef6b788b1ea | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1c587f30c6242cc37b3d6ee6d91daef84e51633f
- git.kernel.org/stable/c/21650fe221ea9b72809140b691589dde8bff3eab
- git.kernel.org/stable/c/50c3c7df4f26d36b30bc950a7d780f7029fd52f8
- git.kernel.org/stable/c/94344bc7c9d70b04be718d841b92873aa3ea8191
- git.kernel.org/stable/c/d88071a6ce091272726bedda26c105b85b23705f
- git.kernel.org/stable/c/ee717e73ab47253c82c134c342e32fcdfcfccd87
- git.kernel.org/stable/c/ef8c9dacda2871accd64e3eda951fef6b788b1ea
Vendor advisories and official records. Exploit/PoC links are deliberately left out.