CVE-2021-47601: tee: amdtee: fix an IS_ERR() vs NULL bug
In the Linux kernel, the following vulnerability has been resolved:
tee: amdtee: fix an IS_ERR() vs NULL bug
The __get_free_pages() function does not return error pointers it returns
NULL so fix this condition to avoid a NULL dereference.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in AMD Trusted Execution Environment support. Under memory pressure, the driver could treat a failed allocation incorrectly and dereference NULL, likely causing a kernel crash. The source bundle does not provide CVSS, confirmed exploitation, or a vendor-specific operational impact rating.
Executive priority
Treat this as a patch-management item until vendor scoring or exploitation evidence changes. It can affect kernel stability on relevant AMD Linux systems, but the provided sources do not support emergency prioritization across all Linux assets.
Technical view
__get_free_pages() returns NULL on failure, not an error pointer. The amdtee code tested the result with IS_ERR(), so a failed allocation could pass the check and be dereferenced. Linux stable commits correct the error handling. The bundle lists Linux kernel versions including 5.6, 5.10.88, 5.15.11, and 5.16 as affected.
Likely exposure
Exposure appears limited to Linux systems using vulnerable kernels with AMD TEE amdtee support present and reachable. Organizations should prioritize validation on AMD-based Linux hosts, appliances, or images that include this driver. The provided data is insufficient to determine default exploitability or affected distributions.
Exploitation context
The bundle shows KEV status as false and provides no evidence of active exploitation or public weaponization. The described failure mode is a NULL dereference after allocation failure, which most directly suggests denial of service if the affected path can be triggered.
Researcher notes
Key issue is incorrect error handling: IS_ERR() was used for an allocator that returns NULL. Evidence is limited to the CVE description and Linux stable references; no CWE, CVSS, trigger preconditions, privilege requirements, or distribution-specific package status are supplied.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check distribution vendor advisories for packaged kernel availability and backports.
Prioritize AMD Linux systems that expose or use TEE functionality.
If immediate patching is delayed, review vendor guidance for amdtee-specific risk reduction.
Validation and detection
Inventory Linux kernel versions across AMD-based servers, endpoints, and appliances.
Check whether amdtee support is built, loaded, or packaged in deployed kernels.
Compare deployed kernels against distribution advisories and the referenced stable commits.
Review crash logs for kernel NULL dereference events involving amdtee or TEE paths.
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-47601 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.