CVE-2022-49370: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle
In the Linux kernel, the following vulnerability has been resolved:
firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle
kobject_init_and_add() takes reference even when it fails.
According to the doc of kobject_init_and_add()
If this function returns an error, kobject_put() must be called to
properly clean up the memory associated with the object.
Fix this issue by calling kobject_put().
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a local denial-of-service risk. A low-privileged local user may be able to trigger a memory leak in the dmi-sysfs firmware interface, potentially degrading availability. It is not described as a remote compromise, data theft, or integrity issue in the provided sources.
Executive priority
Handle through normal kernel patch management, with higher priority for multi-user or shared compute environments. This is a moderate availability risk, not an internet-facing emergency based on the supplied evidence.
Technical view
CVE-2022-49370 is a CWE-401 memory leak in Linux firmware dmi-sysfs. dmi_sysfs_register_handle used kobject_init_and_add(), which keeps a reference even on failure. The fix calls kobject_put() on the error path. CVSS 3.1 is 5.5: local access, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions listed in the CVE record, especially shared systems where untrusted local users exist. Network-only exposure is not supported by the provided sources.
Exploitation context
The CVE is not in KEV, and the provided sources do not report active exploitation or public exploit tooling. The documented impact is local availability loss through memory leakage, not confidentiality or integrity compromise.
Researcher notes
The key validation point is the kobject lifetime error path in dmi_sysfs_register_handle. The provided fix rationale is explicit, but sources do not describe triggering conditions, proof-of-concept code, or exploitation in the wild.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable fixes.
Prioritize shared Linux systems with local shell, container, or workload access.
Check Linux stable commit guidance if vendor guidance is not yet available.
Monitor affected hosts for abnormal memory pressure until patched.
Validation and detection
Inventory running Linux kernel versions against the CVE affected version data.
Verify the deployed kernel includes the relevant stable fix commit for its branch.
Confirm vulnerability scanners no longer report CVE-2022-49370 after update.
Review whether untrusted local users can access affected systems.
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.