Skip to main content

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Propagate SMU errors and validate S2D address… (CVE-2026-81016)

0
Medium
Published: 09/11/2026 (09/11/2026, 21:31:24 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's AMD platform code was resolved involving improper handling of SMU command errors and uninitialized physical address values. The function amd_stb_s2d_init() ignored return values from several SMU commands, leading to potential use of uninitialized addresses in memory mapping operations. This could cause incorrect memory mappings and kernel warnings.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/12/2026, 01:19:23 UTC

Technical Analysis

The Linux kernel vulnerability (CVE-2026-81016) affects the AMD platform code where the amd_stb_s2d_init() function discards return values from S2D SMU commands. When the SMU refuses a command, the failure is only indirectly noticed and reported as a generic error, masking the real issue. More critically, the physical address low/high values returned by the SMU are ignored on failure, leaving them uninitialized. This uninitialized address is then passed to devm_ioremap(), potentially mapping physical address zero and triggering kernel warnings about ioremap on RAM. The fix involves checking and propagating the return value of each SMU command and rejecting zero physical addresses before calling devm_ioremap().

Potential Impact

The vulnerability can lead to improper memory mappings in the kernel due to uninitialized physical addresses, which may cause kernel warnings and potentially unstable behavior. The error masking also hinders accurate error detection and handling in the affected code path. There is no indication of active exploitation or direct compromise from this issue.

Mitigation Recommendations

A fix has been implemented in the Linux kernel to properly check and propagate SMU command return values and to reject zero physical addresses before memory mapping. Users should apply the official kernel updates that include this fix. Since this is a kernel-level vulnerability, updating to a patched kernel version is the recommended remediation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-wv8r-9hh3-p28x
Osv Schema Version
1.4.0
Aliases
["CVE-2026-81016"]

Threat ID: 6aa4a02755bf5e2cf5a86b08

Added to database: 09/12/2026, 00:43:19 UTC

Last enriched: 09/12/2026, 01:19:23 UTC

Last updated: 09/12/2026, 01:19:23 UTC

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses