UBUNTU-CVE-2026-93179: Medium severity ubuntu/linux-aws vulnerability
In the Linux kernel, the following vulnerability has been resolved: drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read Reject voltage objects whose usSize is smaller than the header or would advance the cursor past the table end, preventing an infinite loop or heap OOB read when the VBIOS supplies a malformed VoltageObjectInfo table.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
What systems are exposed to this issue?
The affected software list includes Ubuntu Linux kernel packages for the standard, AWS, Azure, GCP, FIPS, AWS FIPS, Azure FIPS, and GCP FIPS variants. Exposure depends on the AMD DRM powerplay code processing a malformed VoltageObjectInfo table supplied by VBIOS.
What does an attacker need to trigger the flaw?
The vulnerable condition requires a malformed VoltageObjectInfo table from VBIOS. The provided data does not establish a remote attack path, required privileges, or whether an attacker can alter the relevant VBIOS data.
What is the impact if the malformed table is processed?
A VoltageObjectInfo entry with an invalid usSize can cause a zero-stride loop or a heap out-of-bounds read. The supplied severity vector indicates availability impact is high, while confidentiality and integrity impact are listed as none.
What is the mitigation described by the fix?
The fix rejects voltage objects whose usSize is smaller than the header or would move the parser cursor beyond the end of the table. This prevents the infinite loop and heap out-of-bounds read during parsing.