PatchSiren cyber security CVE debrief
CVE-2026-93178 Linux CVE debrief
A bounds-checking vulnerability was resolved in the Linux kernel's drm/amdgpu/pm/powerplay, specifically in the SMU7 lookup. The vulnerability arises from the use of vddInd and vddcInd fields from VBIOS-parsed tables to index into voltage lookup tables without a bounds check. This could potentially lead to system instability or denial of service if exploited.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-09-18
Who should care
Linux system administrators and security teams should assess exposure and verify system configurations. Operators of Linux-based systems, especially those using the affected kernel versions, need to prioritize patching or mitigating this vulnerability to prevent potential system instability or denial of service. Security teams should review system configurations and ensure that patches or mitigations are applied promptly.
Why it matters
A bounds-checking vulnerability in the Linux kernel's drm/amdgpu/pm/powerplay requires verification of system exposure and prompt patching or mitigation to prevent potential system instability or denial of service.
- Potential system instability or denial of service
- Need for verification of system configurations and exposure
- Priority for patching or mitigating vulnerable systems
Technical summary
The Linux kernel's drm/amdgpu/pm/powerplay does not perform bounds checking on vddInd and vddcInd fields from VBIOS-parsed tables when indexing into voltage lookup tables. This could lead to system instability if invalid indices are used. The vulnerability arises from the use of these fields to index into voltage lookup tables without a bounds check, potentially causing denial of service or system instability if exploited. Affected systems require verification of exposure and prompt patching or mitigation to prevent potential impacts.
Defensive priority
Medium
Recommended defensive actions
- Review Linux kernel updates for patched versions
- Verify system configurations for exposure
- Monitor system stability and performance
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
Evidence notes
The CVE record and NVD entry provide details on the vulnerability. However, the scope of affected systems and potential impact require further verification from official Linux kernel sources. Affected Linux kernel versions and configurations need to be assessed for exposure. Defenders should verify system configurations and apply patches or mitigations as needed. The vulnerability's impact on system stability and potential denial of service necessitates prompt attention.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-93178 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-93178
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-93178 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93178
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/1664327ce797e09e387dc10cbbaa5b8d76558d2c
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/3a8a05477cda6c8293e2b629495b42981dcaba32
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6f08c001fa6e8212930d694540ae8d9d6d3fb58a
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/745297208d31222f916cc04da313cb737b997935
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/8a3db9f593b643904c6cc6d8a3f211c84ca6cf8a
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/ce0d8e72836c9d3710a160ad848b0f1d096075e3
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d9ef085114d1e3c2c1f869c0bdb275a7b358ce8b
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f925d317d84d401d642e537ea18ee12f67cb6983
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.