CVE-2021-47134: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: efi/fdt: fix panic when no valid fdt found setup_arch() would invoke efi_init()->efi_get_fdt_params(). If no valid fdt found then initial_boot_params will be null. So we should stop further fdt processing here. I encountered this issue on risc-v.
AI Analysis
Technical Summary
CVE-2021-47134 is a vulnerability identified in the Linux kernel related to the handling of the Flattened Device Tree (FDT) during the early boot process, specifically within the EFI (Extensible Firmware Interface) initialization code. The vulnerability arises in the setup_arch() function, which calls efi_init() and subsequently efi_get_fdt_params(). If no valid FDT is found, the initial_boot_params pointer becomes null. However, the kernel code did not properly halt further FDT processing in this scenario, which could lead to a kernel panic. This issue was notably observed on the RISC-V architecture, where the absence of a valid FDT triggers the panic. The FDT is critical for describing hardware layout to the kernel at boot time, and improper handling of its absence can cause system instability or denial of service. Although this vulnerability does not appear to have an associated CVSS score and no known exploits are reported in the wild, it represents a stability and availability risk for affected Linux systems, particularly those running on RISC-V or similar architectures where FDT usage is common. The vulnerability was resolved by adding a check to stop further FDT processing when no valid FDT is found, preventing the kernel panic.
Potential Impact
For European organizations, the primary impact of CVE-2021-47134 is on system availability and stability. Systems running Linux kernels affected by this vulnerability may experience unexpected kernel panics during boot if the FDT is missing or invalid, leading to denial of service conditions. This could disrupt critical infrastructure, embedded systems, or servers that rely on Linux, especially those using RISC-V or other architectures where FDT is essential. While the vulnerability does not directly compromise confidentiality or integrity, the resulting downtime could affect business operations, service availability, and potentially lead to financial losses or reputational damage. Organizations deploying Linux in embedded devices, industrial control systems, or cloud environments with custom kernel builds should be particularly cautious. Since no known exploits exist, the immediate threat level is moderate, but unpatched systems remain vulnerable to accidental or intentional triggering of the kernel panic.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the latest Linux kernel updates and patches that address CVE-2021-47134, ensuring the fix that halts FDT processing when no valid FDT is found is included. 2) Validate the presence and correctness of the FDT in their boot configurations, especially for RISC-V and other affected architectures, to prevent boot-time failures. 3) Implement robust monitoring and alerting for kernel panics or boot failures to enable rapid response. 4) For embedded or specialized Linux deployments, conduct thorough testing of boot sequences with various FDT configurations to detect potential issues early. 5) Maintain an inventory of Linux kernel versions in use across infrastructure to identify and prioritize vulnerable systems for patching. 6) Consider fallback or recovery mechanisms such as bootloader configurations that can recover from failed boots caused by this issue.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland
CVE-2021-47134: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: efi/fdt: fix panic when no valid fdt found setup_arch() would invoke efi_init()->efi_get_fdt_params(). If no valid fdt found then initial_boot_params will be null. So we should stop further fdt processing here. I encountered this issue on risc-v.
AI-Powered Analysis
Technical Analysis
CVE-2021-47134 is a vulnerability identified in the Linux kernel related to the handling of the Flattened Device Tree (FDT) during the early boot process, specifically within the EFI (Extensible Firmware Interface) initialization code. The vulnerability arises in the setup_arch() function, which calls efi_init() and subsequently efi_get_fdt_params(). If no valid FDT is found, the initial_boot_params pointer becomes null. However, the kernel code did not properly halt further FDT processing in this scenario, which could lead to a kernel panic. This issue was notably observed on the RISC-V architecture, where the absence of a valid FDT triggers the panic. The FDT is critical for describing hardware layout to the kernel at boot time, and improper handling of its absence can cause system instability or denial of service. Although this vulnerability does not appear to have an associated CVSS score and no known exploits are reported in the wild, it represents a stability and availability risk for affected Linux systems, particularly those running on RISC-V or similar architectures where FDT usage is common. The vulnerability was resolved by adding a check to stop further FDT processing when no valid FDT is found, preventing the kernel panic.
Potential Impact
For European organizations, the primary impact of CVE-2021-47134 is on system availability and stability. Systems running Linux kernels affected by this vulnerability may experience unexpected kernel panics during boot if the FDT is missing or invalid, leading to denial of service conditions. This could disrupt critical infrastructure, embedded systems, or servers that rely on Linux, especially those using RISC-V or other architectures where FDT is essential. While the vulnerability does not directly compromise confidentiality or integrity, the resulting downtime could affect business operations, service availability, and potentially lead to financial losses or reputational damage. Organizations deploying Linux in embedded devices, industrial control systems, or cloud environments with custom kernel builds should be particularly cautious. Since no known exploits exist, the immediate threat level is moderate, but unpatched systems remain vulnerable to accidental or intentional triggering of the kernel panic.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the latest Linux kernel updates and patches that address CVE-2021-47134, ensuring the fix that halts FDT processing when no valid FDT is found is included. 2) Validate the presence and correctness of the FDT in their boot configurations, especially for RISC-V and other affected architectures, to prevent boot-time failures. 3) Implement robust monitoring and alerting for kernel panics or boot failures to enable rapid response. 4) For embedded or specialized Linux deployments, conduct thorough testing of boot sequences with various FDT configurations to detect potential issues early. 5) Maintain an inventory of Linux kernel versions in use across infrastructure to identify and prioritize vulnerable systems for patching. 6) Consider fallback or recovery mechanisms such as bootloader configurations that can recover from failed boots caused by this issue.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-03-04T18:12:48.840Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9834c4522896dcbe9e1f
Added to database: 5/21/2025, 9:09:08 AM
Last enriched: 6/26/2025, 7:50:59 PM
Last updated: 8/7/2025, 10:30:55 AM
Views: 14
Related Threats
CVE-2025-8991: Business Logic Errors in linlinjava litemall
MediumCVE-2025-8990: SQL Injection in code-projects Online Medicine Guide
MediumCVE-2025-8940: Buffer Overflow in Tenda AC20
HighCVE-2025-8939: Buffer Overflow in Tenda AC20
HighCVE-2025-50518: n/a
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.