Availability loss via unvalidated PCIe lane settings
Published Aug 13, 2024 · Updated Nov 4, 2024
Improper input validation in AMD Radeon RX 6000 and PRO W6000 SMU firmware allows local users to cause availability loss through PCIe changes. The SMU accepts lane-count and lane-speed changes from a compromised PCIe physical function without adequately validating the specified quantities. Administrative privileges and control of a compromised physical function are required, and the published consequence is limited to availability.
Summary
What happened
Improper input validation in AMD Radeon RX 6000 and PRO W6000 SMU firmware allows local users to cause availability loss through PCIe changes. The SMU accepts lane-count and lane-speed changes from a compromised PCIe physical function without adequately validating the specified quantities. Administrative privileges and control of a compromised physical function are required, and the published consequence is limited to availability.
The record
- CVE
- CVE-2023-31304
- Published
- Aug 13, 2024
- Updated
- Nov 4, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Radeon PRO W6000 Series Graphics
- Classifications
- CWE-1284, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2024Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo