Kernel memory corruption via stale phandle reference
Published May 17, 2024 · Updated Aug 5, 2026
Double free in the Open Firmware parser in Linux allows local users to corrupt kernel memory through a malformed phandle map. The of_parse_phandle_with_args_map() inner loop calls of_node_put(new) on a stale reference because new is not reset after being assigned to cur between outer-loop iterations. Reaching the path requires local low-privileged access and a crafted device-tree mapping; triggering it can destabilize the kernel or alter kernel-controlled memory.
Summary
What happened
Double free in the Open Firmware parser in Linux allows local users to corrupt kernel memory through a malformed phandle map. The of_parse_phandle_with_args_map() inner loop calls of_node_put(new) on a stale reference because new is not reset after being assigned to cur between outer-loop iterations. Reaching the path requires local low-privileged access and a crafted device-tree mapping; triggering it can destabilize the kernel or alter kernel-controlled memory.
The record
- CVE
- CVE-2023-52679
- Published
- May 17, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.17
- Affected versionversion=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa <26b4d702c44f9e5cf3c5c001ae619a4a001889db
- Affected versionversion=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa <4541004084527ce9e95a818ebbc4e6b293ffca21
- Affected versionversion=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa <4dde83569832f9377362e50f7748463340c5db6b
- Affected versionversion=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa <a0a061151a6200c13149dbcdb6c065203c8425d2
- Affected versionversion=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa <b64d09a4e8596f76d27f4b4a90a1cf6baf6a82f8
- Affected versionversion=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa <b9d760dae5b10e73369b769073525acd7b3be2bd
- Affected versionversion=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa <cafa992134124e785609a406da4ff2b54052aff7
- Affected versionversion=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa <d5f490343c77e6708b6c4aa7dbbfbcbb9546adea
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo