CVE-2026-80651
Last modified
CVE-2026-80651 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: crypto: ccp/sev-dev-tsm - bail out early when pdev->bus is NULL dsm_create() initially checks pdev->bus when computing segment_id: u8 segment_id = pdev->bus ? pci_domain_nr(pdev->bus) : 0; But the next two lines unconditionally dereference pdev->bus via pcie_find_root_port() and especially pci_dev_id(pdev), which expands to PCI_DEVID(dev->bus->number, dev->devfn). If pdev->bus is in fact NULL, segment_id is initialised to 0 but the very next statement crashes the kernel. smatch flags this: drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we previously assumed 'pdev->bus' could be null (see line 251) Make the NULL handling consistent: if pdev->bus is NULL the device has no PCI context to work with and SEV TIO setup cannot proceed, so return -ENODEV before any of the bus-dependent lookups.
Description
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp/sev-dev-tsm - bail out early when pdev->bus is NULL dsm_create() initially checks pdev->bus when computing segment_id: u8 segment_id = pdev->bus ? pci_domain_nr(pdev->bus) : 0; But the next two lines unconditionally dereference pdev->bus via pcie_find_root_port() and especially pci_dev_id(pdev), which expands to PCI_DEVID(dev->bus->number, dev->devfn). If pdev->bus is in fact NULL, segment_id is initialised to 0 but the very next statement crashes the kernel. smatch flags this: drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we previously assumed 'pdev->bus' could be null (see line 251) Make the NULL handling consistent: if pdev->bus is NULL the device has no PCI context to work with and SEV TIO setup cannot proceed, so return -ENODEV before any of the bus-dependent lookups. The remaining initialisation now runs only on the path where pdev->bus is known to be valid. No change for callers where pdev->bus is non-NULL, which is the only case where dsm_create() did meaningful work before this change.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 4be423572da1f4c11f45168e3fafda870ddac9f8, < 6bafd740095fb3d0e9a00540bc8f3484c38e6f85; >= 4be423572da1f4c11f45168e3fafda870ddac9f8, < 930d9d36ea618a775985446a125aedeb401db522 |
| Linux | Linux | 6.19 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-80651?
How severe is CVE-2026-80651?
How do I fix CVE-2026-80651?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-80645In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-80646In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-80647In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80648In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80649In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-80650In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80652In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80653In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-80654In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80655In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80656In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-80657In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-80651?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
