CVE-2026-23137: of: unittest: Fix memory leak in unittest_data_add()
In the Linux kernel, the following vulnerability has been resolved:
of: unittest: Fix memory leak in unittest_data_add()
In unittest_data_add(), if of_resolve_phandles() fails, the allocated
unittest_data is not freed, leading to a memory leak.
Fix this by using scope-based cleanup helper __free(kfree) for automatic
resource cleanup. This ensures unittest_data is automatically freed when
it goes out of scope in error paths.
For the success path, use retain_and_null_ptr() to transfer ownership
of the memory to the device tree and prevent double freeing.
Security readout for executives and security teams
Plain-English summary
This CVE describes a Linux kernel memory leak in device-tree unit-test code. If a phandle resolution error occurs, allocated memory is not released. The supplied sources do not show active exploitation or a CVSS score. Business urgency appears low unless your environment exercises this kernel unittest path or carries affected kernel builds.
Executive priority
Track through normal Linux kernel patch management unless internal evidence shows this unittest path is reachable in production. No source-provided evidence supports emergency response, active exploitation, or broad remote impact.
Technical view
In unittest_data_add(), a failure from of_resolve_phandles() leaves unittest_data allocated. The fix uses __free(kfree) for scope-based cleanup and retain_and_null_ptr() on success to transfer ownership safely. References point to Linux stable commits addressing the leak.
Likely exposure
Exposure is likely limited to Linux systems with affected kernel versions where the relevant device-tree unittest code can run. The bundle lists Linux as affected across broad version metadata, but exact downstream package exposure requires vendor kernel mapping.
Exploitation context
The supplied sources do not report active exploitation, and KEV is false. No public exploit, attack path, privilege requirement, or remote trigger is provided in the bundle. Treat exploitability as unproven from these sources.
Researcher notes
Key uncertainty is reachability. The CVE describes a memory leak on an error path, but the bundle does not define attacker control, required privileges, or operational impact. Validate against actual kernel source, configuration, and distribution backports.
Mitigation direction
Update affected Linux kernels to vendor builds containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes and package-specific status.
Prioritize systems that enable or run kernel device-tree unittest functionality.
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.
cve · low confidence lookup
CVE-2026-23137 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 14, 2026, 15:22 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.