CVE-2021-47567: powerpc/32: Fix hardlockup on vmap stack overflow
In the Linux kernel, the following vulnerability has been resolved:
powerpc/32: Fix hardlockup on vmap stack overflow
Since the commit c118c7303ad5 ("powerpc/32: Fix vmap stack - Do not
activate MMU before reading task struct") a vmap stack overflow
results in a hard lockup. This is because emergency_ctx is still
addressed with its virtual address allthough data MMU is not active
anymore at that time.
Fix it by using a physical address instead.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects 32-bit PowerPC systems. Under a vmap stack overflow condition, the kernel can hard lock because it references an emergency context through a virtual address while the data MMU is inactive. The documented impact is system unavailability, not data theft or privilege escalation.
Executive priority
Give this targeted attention if the organization runs 32-bit PowerPC Linux, especially in embedded or operational technology contexts. For mainstream server fleets without PowerPC, urgency is likely low, but confirm inventory before dismissing it.
Technical view
The fix changes powerpc/32 vmap stack overflow handling to use a physical address for emergency_ctx. The regression followed commit c118c7303ad5. The source bundle lists Linux affected versions and three stable kernel commits, but does not provide CVSS, CWE, exploitability, or detailed affected-range semantics.
Likely exposure
Exposure appears limited to Linux deployments running affected 32-bit PowerPC kernels. Most general x86_64 or non-PowerPC Linux fleets are not implicated by the provided evidence. Version data in the bundle is incomplete, so confirm through vendor kernel advisories or backport records.
Exploitation context
The sources do not report active exploitation, and this CVE is not marked in KEV. The described trigger is a vmap stack overflow leading to hard lockup. Treat this primarily as an availability risk unless vendor evidence says otherwise.
Researcher notes
Evidence is narrow and kernel-specific. The source bundle identifies the bug, the regression commit, and stable fixes, but lacks CVSS, CWE, proof-of-concept status, and precise version-range metadata. Avoid broader claims beyond 32-bit PowerPC Linux availability impact.
Mitigation direction
Identify any 32-bit PowerPC Linux systems in production or embedded environments.
Update to a vendor kernel containing one of the referenced stable fixes.
For appliances, request the vendor’s CVE-2021-47567 fix or backport status.
Prioritize systems where kernel lockups would affect safety, availability, or recovery time.
Validation and detection
Inventory kernel architecture and version across Linux assets.
Check whether deployed kernels include the referenced stable commit or vendor backport.
Review vendor advisories for exact affected and fixed package versions.
Correlate unexplained PowerPC hard lockups with affected kernel versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47567 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.