CVE-2022-49757: EDAC/highbank: Fix memory leak in highbank_mc_probe()
In the Linux kernel, the following vulnerability has been resolved:
EDAC/highbank: Fix memory leak in highbank_mc_probe()
When devres_open_group() fails, it returns -ENOMEM without freeing memory
allocated by edac_mc_alloc().
Call edac_mc_free() on the error handling path to avoid a memory leak.
[ bp: Massage commit message. ]
Security readout for executives and security teams
Plain-English summary
CVE-2022-49757 is a Linux kernel memory leak in the EDAC highbank driver error path. A local low-privileged user could potentially trigger resource exhaustion and affect availability. The public data does not show remote exposure or data theft impact.
Executive priority
Treat as a moderate Linux availability issue. It should be handled through normal kernel patch management, with higher priority for systems using the highbank EDAC path or where local users can run code.
Technical view
In highbank_mc_probe(), failure of devres_open_group() returned -ENOMEM without freeing memory allocated by edac_mc_alloc(). The fix adds edac_mc_free() on that error path. CVSS 3.1 is 5.5: local attack, low complexity, low privileges, no confidentiality or integrity impact, high availability impact.
Likely exposure
Exposure appears limited to affected Linux kernel versions where the EDAC highbank driver code is present and reachable. The source bundle lists Linux as affected, but does not provide distribution-specific package status or confirm which deployed configurations load this driver.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The impact is availability-focused through a memory leak, requiring local access with low privileges according to the CVSS vector.
Researcher notes
Evidence supports CWE-401 memory leak in a Linux kernel driver probe error path. The bundle names stable kernel commits but does not include exploit details, distribution mappings, or proof of active exploitation.
Mitigation direction
Apply a vendor kernel update containing the EDAC highbank fix.
Check Linux distribution advisories for package-specific fixed versions.
Prioritize systems running affected kernels with EDAC highbank enabled.
If no vendor package exists, assess the listed stable kernel commits.
Monitor for abnormal memory consumption on potentially affected hosts.
Validation and detection
Inventory kernel versions across Linux systems.
Check whether EDAC highbank code is built, enabled, or loaded.
Compare kernel source or package changelog against listed stable commits.
Confirm updated systems include the edac_mc_free() error-path fix.
Record unsupported or unpatched affected kernels for remediation tracking.
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.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.