Security readout for executives and security teams
Plain-English summary
This is a Linux kernel resource leak in the EDAC/versalnet driver. A device tree reference was not released during probe handling, causing kernel memory to be leaked. The public record does not provide CVSS, known exploitation, or broad business impact evidence.
Executive priority
Treat as routine patch management unless validation shows critical embedded or operational systems use this driver. There is no supplied evidence of active exploitation or high-impact compromise.
Technical view
The bug is in mc_probe(): of_parse_phandle() returns a device_node reference, but r5_core_node was not released on exit paths. The upstream fix uses __free(device_node) so of_node_put() runs automatically when the variable leaves scope.
Likely exposure
Exposure appears limited to Linux systems using affected kernel builds with the EDAC/versalnet code path. Organizations should not assume all Linux servers are exposed; validate kernel version and whether this driver is present or relevant.
Exploitation context
The supplied sources do not report active exploitation, KEV listing, exploitability details, or remote attack conditions. The described impact is a kernel memory leak, not code execution or privilege escalation.
Researcher notes
The evidence supports a device_node reference leak fix only. Affected-version data in the bundle is limited and should be reconciled with kernel stable commits and downstream vendor backports before declaring exposure.
Mitigation direction
- Update to a Linux kernel containing the referenced stable fixes.
- Check Linux distribution advisories for backported fixes.
- Prioritize systems where EDAC/versalnet is built or used.
- Monitor vendor guidance if fixed package versions are not yet clear.
Validation and detection
- Inventory Linux kernel versions across affected environments.
- Check whether EDAC/versalnet support is built, loaded, or deployed.
- Compare kernel source or changelog against the referenced commit IDs.
- Confirm vendor packages include the upstream memory leak fix.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2026-46030 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
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.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/b6e61356ad24987be40bf25369d22dd8dd00a513CVE reference, Linux
- https://git.kernel.org/stable/c/17e136993b2b5111d1ee1c57bbd188ae0bb0e128CVE reference, Linux
- https://git.kernel.org/stable/c/5c709b376460ff322580c41600e31c02f7cc0307CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.