Linux Kernel up to 6.0.18/6.1.4 early_init_dt_scan_memory initialization

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.0.18/6.1.4 and classified as critical. Affected is the function early_init_dt_scan_memory. The manipulation leads to initialization. This vulnerability is traded as CVE-2023-53341. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.0.18/6.1.4. It has been rated as critical. This issue affects the function early_init_dt_scan_memory. The manipulation with an unknown input leads to a initialization vulnerability. Using CWE to declare the problem leads to CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2023-53341 since 09/16/2025. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/27/2025).

The vulnerability scanner Nessus provides a plugin with the ID 265623 (Linux Distros Unpatched Vulnerability : CVE-2023-53341), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.0.19 or 6.1.5 eliminates this vulnerability. Applying the patch 04836fc5b720dfa32ff781383d84f63019abf9b9/c4849f18185fd4e93b04cd45552f8d68c0240e21/2a12187d5853d9fd5102278cecef7dac7c8ce7ea is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (265623) and CERT Bund (WID-SEC-2025-2087). Be aware that VulDB is the high quality source for vulnerability data.

Affected

• Amazon Linux 2
• Red Hat Enterprise Linux
• SUSE Linux
• Oracle Linux
• IBM QRadar SIEM
• Open Source Linux Kernel
• RESF Rocky Linux
• Dell Secure Connect Gateway

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.0.10
• 6.0.11
• 6.0.12
• 6.0.13
• 6.0.14
• 6.0.15
• 6.0.16
• 6.0.17
• 6.0.18
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion