CVE-2026-92505Hinoki check available

Unspecified impact via invalid PCI-segment dereference

Published Sep 17, 2026 · Updated Sep 17, 2026

Invalid memory access in Linux 6.17 AMD IOMMU debugfs allows local users to cause unspecified impact via crafted device identifiers. In drivers/iommu/amd/debugfs.c, devid_write dereferences pci_seg->id after an unsuccessful segment lookup leaves the iterator pointing at the list head rather than a valid segment. Reaching the flaw requires write access to the AMD IOMMU devid debugfs file, normally restricted to privileged users; upstream documents undefined behavior without specifying a crash or another operational consequence.

CVSS severity2.3
Low
EPSS probability0.21%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Invalid memory access in Linux 6.17 AMD IOMMU debugfs allows local users to cause unspecified impact via crafted device identifiers. In drivers/iommu/amd/debugfs.c, devid_write dereferences pci_seg->id after an unsuccessful segment lookup leaves the iterator pointing at the list head rather than a valid segment. Reaching the flaw requires write access to the AMD IOMMU devid debugfs file, normally restricted to privileged users; upstream documents undefined behavior without specifying a crash or another operational consequence.

The record

CVE
CVE-2026-92505
Published
Sep 17, 2026
Updated
Sep 17, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. Sep 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 17, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2e98940f123d9c69d4759078aea9a536244c98d3 <843e149989665f8309ad2efe6048dc76591e1f94
  2. Affected versionversion=2e98940f123d9c69d4759078aea9a536244c98d3 <8aabe0fba01486b5d893e708b05a8fa7f1b7efbb
  3. Affected versionversion=2e98940f123d9c69d4759078aea9a536244c98d3 <99d42aef089a07cfb1d404a7227ac9dc7628b497
  4. Affected versionversion=6.17

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

The Linux Kernel Organization · Linuxversion=2e98940f123d9c69d4759078aea9a536244c98d3 <843e149989665f8309ad2efe6048dc76591e1f94; version=2e98940f123d9c69d4759078aea9a536244c98d3 <8aabe0fba01486b5d893e708b05a8fa7f1b7efbb; version=2e98940f123d9c69d4759078aea9a536244c98d3 <99d42aef089a07cfb1d404a7227ac9dc7628b497; version=6.17

Published CVSS scores

2.3Amazon LinuxCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started