cve.bz

CVE-2021-47465 linux linux kernel: Uncontrolled Recursion

5.5 mediumEPSS 0.2%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: KVM: PPC: Book3S HV: Fix stack handling in idle_kvm_start_guest() In commit 10d91611f426 ("powerpc/64s: Reimplement book3s idle code in C") kvm_start_guest() became idle_kvm_start_guest(). The old code allocated a stack frame on the emergency stack, but didn't use the frame to store anything, and also didn't store anything in its caller's frame. idle_kvm_start_guest() on the other hand is written more like a normal C function, it creates a frame on entry, and also stores CR/LR into its callers frame (per the ABI). The problem is that there is no caller frame on the emergency stack. The emergency stack for a given CPU is allocated with: paca_ptrs[i]->emergency_sp = alloc_stack(limit, i) + THREAD_SIZE; So emergency_sp actually points to the first address above the emergency stack allocation for a given CPU, we must not store above it without first decrementing it to create a frame. This is different to the regular kernel stack, paca->kstack, which is initialised to point at an initial frame that is ready to use. idle_kvm_start_guest() stores the backchain, CR and LR all of which write outside the allocation for the emergency stack. It then creates a stack frame and saves the non-volatile registers. Unfortunately the frame it creates is not large enough to fit the non-volatiles, and so the saving of the non-volatile registers also writes outside the emergency stack allocation. The end result is that we corrupt whatever is at 0-24 bytes, and 112-248 bytes above the emergency stack allocation. In practice this has gone unnoticed because the memory immediately above the emergency stack happens to be used for other stack allocations, either another CPUs mc_emergency_sp or an IRQ stack. See the order of calls to irqstack_early_init() and emergency_stack_init(). The low addresses of another stack are the top of that stack, and so are only used if that stack is under extreme pressue, which essentially never happens in practice - and if it did there's a high likelyhood we'd crash due to that stack overflowing. Still, we shouldn't be corrupting someone else's stack, and it is purely luck that we aren't corrupting something else. To fix it we save CR/LR into the caller's frame using the existing r1 on entry, we then create a SWITCH_FRAME_SIZE frame (which has space for pt_regs) on the emergency stack with the backchain pointing to the existing stack, and then finally we switch to the new frame on the emergency stack.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-05-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-674 Uncontrolled Recursion
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-47465 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-47465?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-47465?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-47465 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.2 and later

Fixed in

ProductRelease lineFixed in
Linux5.45.4.156
Linux5.105.10.76
Linux5.145.14.15
Linuxlater releases5.15

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14linux5.14.16-1DEBIAN-CVE-2021-47465
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2021-47465
Ubuntu18.04:LTSlinux-aws-5.45.4.0-1061.64~18.04.1UBUNTU-CVE-2021-47465
Ubuntu18.04:LTSlinux-azure-5.45.4.0-1065.68~18.04.1UBUNTU-CVE-2021-47465
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2021-47465
Ubuntu18.04:LTSlinux-gcp-5.4, linux-oracle-5.45.4.0-1059.63~18.04.1UBUNTU-CVE-2021-47465
Ubuntu18.04:LTSlinux-hwe-5.45.4.0-92.103~18.04.2UBUNTU-CVE-2021-47465
Ubuntu18.04:LTSlinux-raspi-5.45.4.0-1048.53~18.04.1UBUNTU-CVE-2021-47465
Ubuntu20.04:LTSlinux5.4.0-92.103UBUNTU-CVE-2021-47465
Ubuntu20.04:LTSlinux-aws5.4.0-1061.64UBUNTU-CVE-2021-47465
Ubuntu20.04:LTSlinux-azure5.4.0-1065.68UBUNTU-CVE-2021-47465
Ubuntu20.04:LTSlinux-bluefield5.4.0-1023.26UBUNTU-CVE-2021-47465
Ubuntu20.04:LTSlinux-gcp, linux-oracle5.4.0-1059.63UBUNTU-CVE-2021-47465
12 more for Ubuntu in the JSON and on Ubuntu's page.
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-64kb, kernel-docs, kernel-syms and 4 more5.3.18-150300.59.164.1SUSE-SU-2024:2185-1
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise Micro 5.1 and 3 morekernel-default-base5.3.18-150300.59.164.1.150300.18.96.1SUSE-SU-2024:2185-1
SUSELinux Enterprise High Availability Extension 15 SP2, Linux Enterprise Live Patching 15 SP2kernel-default5.3.18-150200.24.194.1SUSE-SU-2024:2183-1
SUSELinux Enterprise High Availability Extension 15 SP3, Linux Enterprise Live Patching 15 SP3, Linux Enterprise Micro 5.1 and 1 morekernel-default5.3.18-150300.59.164.1SUSE-SU-2024:2185-1
SUSELinux Enterprise High Availability Extension 15 SP4, Linux Enterprise Live Patching 15 SP4, Linux Enterprise Micro 5.3 and 2 morekernel-default5.14.21-150400.24.122.2SUSE-SU-2024:2189-1
SUSELinux Enterprise High Availability Extension 15 SP5, Linux Enterprise Live Patching 15 SP5, Linux Enterprise Micro 5.5 and 2 morekernel-default5.14.21-150500.55.68.1SUSE-SU-2024:2190-1
SUSELinux Enterprise High Performance Computing 15 SP2-LTSS, Linux Enterprise Server 15 SP2-LTSS, Linux Enterprise Server for SAP Applications 15 SP2kernel-default-base5.3.18-150200.24.194.1.150200.9.99.1SUSE-SU-2024:2183-1
SUSELinux Enterprise High Performance Computing 15 SP2-LTSS, Linux Enterprise Server 15 SP2-LTSS, Linux Enterprise Server for SAP Applications 15 SP2kernel-docs, kernel-syms, kernel-source and 3 more5.3.18-150200.24.194.1SUSE-SU-2024:2183-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSSkernel-64kb, kernel-docs, kernel-default and 1 more5.14.21-150400.24.122.2SUSE-SU-2024:2189-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Micro 5.3 and 5 morekernel-default-base5.14.21-150400.24.122.2.150400.24.58.2SUSE-SU-2024:2189-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Server 15 SP4-LTSS and 3 morekernel-syms, kernel-source5.14.21-150400.24.122.1SUSE-SU-2024:2189-1
SUSELinux Enterprise Live Patching 15 SP2kernel-livepatch-SLE15-SP2_Update_491-150200.5.3.1SUSE-SU-2024:2183-1
17 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 15.5dtb-aarch64, kernel-64kb, kernel-docs and 8 more5.14.21-150500.55.68.1SUSE-SU-2024:2190-1
openSUSELeap 15.5kernel-azure, kernel-syms-azure, kernel-source-azure5.14.21-150500.33.57.1SUSE-SU-2024:2019-1
openSUSELeap 15.5kernel-default-base5.14.21-150500.55.68.1.150500.6.31.1SUSE-SU-2024:2190-1
openSUSELeap 15.5kernel-rt, kernel-syms-rt, kernel-rt_debug and 1 more5.14.21-150500.13.58.1SUSE-SU-2024:2008-1
openSUSELeap Micro 5.3, Leap Micro 5.4kernel-default5.14.21-150400.24.122.2SUSE-SU-2024:2189-1
openSUSELeap Micro 5.3, Leap Micro 5.4kernel-default-base5.14.21-150400.24.122.2.150400.24.58.2SUSE-SU-2024:2189-1
openSUSELeap Micro 5.3, Leap Micro 5.4kernel-rt5.14.21-150400.15.82.1SUSE-SU-2024:2011-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelOut of support scope
Red Hat Enterprise Linux 7kernel-rtOut of support scope
Red Hat Enterprise Linux 8kernelWill not fix
Red Hat Enterprise Linux 8kernel-rtWill not fix
Red Hat Enterprise Linux 9kernelWill not fix
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2021-47465.

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON