CVE-2021-46990: powerpc/64s: Fix crashes when toggling entry flush barrier
In the Linux kernel, the following vulnerability has been resolved:
powerpc/64s: Fix crashes when toggling entry flush barrier
The entry flush mitigation can be enabled/disabled at runtime via a
debugfs file (entry_flush), which causes the kernel to patch itself to
enable/disable the relevant mitigations.
However depending on which mitigation we're using, it may not be safe to
do that patching while other CPUs are active. For example the following
crash:
sleeper[15639]: segfault (11) at c000000000004c20 nip c000000000004c20 lr c000000000004c20
Shows that we returned to userspace with a corrupted LR that points into
the kernel, due to executing the partially patched call to the fallback
entry flush (ie. we missed the LR restore).
Fix it by doing the patching under stop machine. The CPUs that aren't
doing the patching will be spinning in the core of the stop machine
logic. That is currently sufficient for our purposes, because none of
the patching we do is to that code or anywhere in the vicinity.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects 64-bit PowerPC systems. Changing the entry flush mitigation at runtime through debugfs could patch live kernel code while other CPUs were running, causing crashes. The business risk is mainly availability and operational instability on affected POWER Linux hosts, not a documented remote compromise path.
Executive priority
Treat as a targeted platform stability issue. Prioritize remediation for POWER Linux infrastructure where kernel crashes could affect production availability, especially systems managed through low-level mitigation controls.
Technical view
The vulnerable behavior is in powerpc/64s entry flush mitigation toggling. Runtime writes to the debugfs entry_flush control trigger kernel self-patching; without stop_machine synchronization, another CPU may execute partially patched code, corrupting return state and crashing. The fix moves patching under stop_machine.
Likely exposure
Exposure is most likely on Linux powerpc/64s systems running affected kernel versions or unpatched stable branches where debugfs entry_flush runtime toggling is available. Non-PowerPC systems are not indicated as affected in the provided sources.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The described trigger is runtime mitigation toggling via debugfs, which commonly implies privileged local operational access, but the sources do not explicitly define required permissions.
Researcher notes
Evidence is limited to the kernel CVE record and stable commit references. No CVSS, CWE, public exploit status, or detailed distribution-specific package status is provided. The key technical condition is unsafe live patching of entry flush code during runtime mitigation toggles.
Mitigation direction
Update affected Linux kernels to a version containing the stable fix.
Prioritize PowerPC 64-bit systems where debugfs is enabled or used operationally.
Avoid runtime entry_flush toggling on unpatched affected systems.
Check Linux distribution advisories for packaged kernel availability and backports.
Validation and detection
Inventory Linux hosts by architecture and kernel version.
Identify PowerPC 64-bit systems using affected stable kernel versions.
Confirm whether the kernel includes the referenced stop_machine patch.
Review operational procedures for debugfs entry_flush changes.
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-46990 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.