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-92505iommu/amd: Fix undefined behavior in devid_write debugfs function

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 32 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 2e98940f123d9c69d4759078aea9a536244c98d3 – < 8aabe0fba01486b5d893e708b05a8fa7f1b7efbb
    • affected 2e98940f123d9c69d4759078aea9a536244c98d3 – < 99d42aef089a07cfb1d404a7227ac9dc7628b497
    • affected 2e98940f123d9c69d4759078aea9a536244c98d3 – < 843e149989665f8309ad2efe6048dc76591e1f94
  • Linux · Linux

    • affected 6.17
    • unaffected < 6.17
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References3

Sources

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

Badge for a README or a ticket

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

Record last updated .