CVE-2022-49011: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new()
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new()
As comment of pci_get_domain_bus_and_slot() says, it returns
a pci device with refcount increment, when finish using it,
the caller must decrement the reference count by calling
pci_dev_put(). So call it after using to avoid refcount leak.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel resource-management bug: a PCI device reference was not released after use. Public sources do not provide a CVSS score, business impact, or evidence of exploitation. Treat it as routine kernel hygiene unless your Linux vendor assigns higher severity.
Executive priority
Schedule remediation through standard Linux kernel maintenance. There is no cited exploitation or severity score, but kernel resource leaks should still be corrected to reduce long-term stability and support risk.
Technical view
The kernel code calls pci_get_domain_bus_and_slot(), which increments a PCI device reference count. The fix adds the required pci_dev_put() call after use to avoid a reference-count leak. Public metadata lists multiple Linux kernel stable branches as affected and provides upstream stable fixes.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or vendor kernels that include the vulnerable code without the backported fix. The sources do not identify remote reachability, privilege requirements, or affected hardware configurations beyond the Linux kernel context.
Exploitation context
No active exploitation is indicated in the provided sources, and this CVE is not listed as KEV in the bundle. The sources describe a refcount leak, not a demonstrated exploit path or direct confidentiality, integrity, or availability impact.
Researcher notes
The CVE text references hwmon/coretemp and also names nv1a_ram_new(), which appears inconsistent. Rely on the linked upstream stable commits and vendor backports for exact code lineage. Public data lacks CVSS, CWE, exploitability details, and concrete impact assessment.
Mitigation direction
Check your Linux distribution’s advisory for CVE-2022-49011 and applicable fixed kernel packages.
Upgrade affected systems to a vendor-supported kernel containing the upstream stable fix.
Prioritize normal kernel patch cycles unless vendor guidance rates this higher.
Track embedded or appliance kernels separately, as fixes may be backported without version changes.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, containers hosts, and appliances.
Compare installed kernels with vendor advisories or the referenced upstream stable commits.
Confirm whether your vendor kernel has backported the pci_dev_put() fix.
Document exceptions where vendor support states the kernel is unaffected.
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-2022-49011 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.