CVE-2023-53341

of/fdt: run soc memory setup when early_init_dt_scan_memory fails

MEDIUM
5.5
CVSS Score
Published: September 17, 2025 at 02:56 PM UTC
Updated: June 17, 2026 at 06:44 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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".

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.17 ≤ v < 6.0.195.17 ≤ v < 6.1.55.17 ≤ v < 6.26.1 ≤ v < 6.1.51f012283e9360fb4007308f04cfaeb205e34b6845.176.2 rc16.2 rc2
Vendor states this is fixed in 04836fc5b720dfa32ff781383d84f63019abf9b9 (fixed)
Vendor states this is fixed in 2a12187d5853d9fd5102278cecef7dac7c8ce7ea (fixed)
Vendor states this is fixed in c4849f18185fd4e93b04cd45552f8d68c0240e21 (fixed)
Vendor states this is fixed in 5.17 (unaffected)
Vendor states this is fixed in 6.0.19 (unaffected)
Vendor states this is fixed in 6.1.5 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-908

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card