Strix
63.2K

CVE-2026-92505

Unknown

Last modified

CVE-2026-92505 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix undefined behavior in devid_write debugfs function When for_each_pci_segment() loop completes without finding a matching segment, the pci_seg pointer is not NULL but points to an invalid memory location (the list head). Accessing pci_seg->id after the loop causes undefined behavior. Fix this by handling the successful case inside the loop and returning -EINVAL after the loop if no matching segment is found..

Description

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix undefined behavior in devid_write debugfs function When for_each_pci_segment() loop completes without finding a matching segment, the pci_seg pointer is not NULL but points to an invalid memory location (the list head). Accessing pci_seg->id after the loop causes undefined behavior. Fix this by handling the successful case inside the loop and returning -EINVAL after the loop if no matching segment is found.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 2e98940f123d9c69d4759078aea9a536244c98d3, < 8aabe0fba01486b5d893e708b05a8fa7f1b7efbb; >= 2e98940f123d9c69d4759078aea9a536244c98d3, < 99d42aef089a07cfb1d404a7227ac9dc7628b497; >= 2e98940f123d9c69d4759078aea9a536244c98d3, < 843e149989665f8309ad2efe6048dc76591e1f94
LinuxLinux6.17

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-92505?
In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix undefined behavior in devid_write debugfs function When for_each_pci_segment() loop completes without finding a matching segment, the pci_seg pointer is not NULL but points to an invalid memory location (the list head). Accessing pci_seg->id after the loop causes undefined behavior. Fix this by handling the successful case inside the loop and returning -EINVAL after the loop if no matching segment is found.
How severe is CVE-2026-92505?
Severity scoring for CVE-2026-92505 is pending analysis.
How do I fix CVE-2026-92505?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-92505?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST