CVE-2023-53341: of/fdt: run soc memory setup when early_init_dt_scan_memory fails
In the Linux kernel, the following vulnerability has been resolved:
of/fdt: run soc memory setup when early_init_dt_scan_memory fails
If memory has been found early_init_dt_scan_memory now returns 1. If
it hasn't found any memory it will return 0, allowing other memory
setup mechanisms to carry on.
Previously early_init_dt_scan_memory always returned 0 without
distinguishing between any kind of memory setup being done or not. Any
code path after the early_init_dt_scan memory call in the ramips
plat_mem_setup code wouldn't be executed anymore. Making
early_init_dt_scan_memory the only way to initialize the memory.
Some boards, including my mt7621 based Cudy X6 board, depend on memory
initialization being done via the soc_info.mem_detect function
pointer. Those wouldn't be able to obtain memory and panic the kernel
during early bootup with the message "early_init_dt_alloc_memory_arch:
Failed to allocate 12416 bytes align=0x40".
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can make some affected systems fail during early boot because memory is not initialized through the fallback SoC path. The practical business impact is availability: devices may panic instead of starting. The source bundle does not show data theft, integrity loss, or active exploitation.
Executive priority
Treat as a moderate availability risk for affected Linux-based appliances and embedded systems. Prioritize patching where device boot reliability matters, especially network edge hardware, but do not treat it as confirmed internet-exploited ransomware-class risk.
Technical view
early_init_dt_scan_memory changed return behavior, but ramips platform memory setup did not continue into soc_info.mem_detect when needed. Boards such as MT7621-based Cudy X6 can fail memory allocation during early boot and panic. CVSS rates this local, low-privilege, availability-only impact.
Likely exposure
Exposure is most likely on Linux systems or firmware using affected kernel versions, especially ramips or MT7621-class embedded devices relying on SoC memory detection. General server exposure is unclear from the provided sources.
Exploitation context
The CVE is not listed as KEV, and the supplied sources do not cite active exploitation. CVSS describes local access with low privileges and no user interaction, causing high availability impact only.
Researcher notes
Evidence supports a kernel boot-time availability failure tied to OF/FDT memory scanning and ramips fallback memory setup. The provided sources do not establish exploit tooling, remote reachability, or broader affected hardware beyond the described board class.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
For embedded devices, request firmware updates from the device or distribution vendor.
Avoid deploying affected kernels on boards that depend on SoC memory detection.
Monitor vendor advisories for backports matching the stable commits.
Validation and detection
Inventory Linux kernel versions against the affected ranges in the CVE record.
Check whether the referenced stable commits are present or backported.
Review early boot logs for early_init_dt_alloc_memory_arch allocation failures.
Prioritize validation on ramips and MT7621-based devices.
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.
cwe · low confidence lookup
CWE-908: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-908 · source CWE mapping
Use of Uninitialized Resource
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.