LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50110: watchdog: sp5100_tco: Fix a memory leak of EFCH MMIO resource

In the Linux kernel, the following vulnerability has been resolved: watchdog: sp5100_tco: Fix a memory leak of EFCH MMIO resource Unlike release_mem_region(), a call to release_resource() does not free the resource, so it has to be freed explicitly to avoid a memory leak.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel watchdog driver bug where an EFCH MMIO resource was released without freeing its resource object, causing a memory leak. The provided sources do not give CVSS, public exploitation, or business-impact evidence beyond kernel reliability risk.

Executive priority

Handle through normal kernel patch management unless your environment broadly uses this watchdog driver on critical Linux hosts. There is no source evidence of active exploitation or high-impact compromise, but kernel memory leaks can still affect service reliability.

Technical view

The issue is in the Linux kernel sp5100_tco watchdog driver. release_resource() was used for an EFCH MMIO resource, but unlike release_mem_region(), it does not free the resource structure. Stable kernel commits correct the cleanup path by explicitly freeing the resource.

Likely exposure

Exposure is most likely limited to Linux systems running affected kernel versions and exercising the sp5100_tco watchdog driver path. The bundle lists affected Linux versions including 5.15.61, 5.18.18, 5.19.2, and 6.0, but does not map distributions or hardware fleets.

Exploitation context

The bundle does not cite active exploitation, exploit availability, KEV listing, or remote attack behavior. Treat this as an unscored kernel memory-leak reliability issue unless vendor advisories provide stronger impact details.

Researcher notes

The key evidence is the kernel commit rationale: release_resource() does not free the resource, so explicit freeing is required. Public data is sparse: no CVSS, CWE, exploit notes, or detailed trigger conditions are included in the bundle.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check distribution advisories for fixed package versions and reboot requirements.
  • Prioritize systems that load or depend on the sp5100_tco watchdog driver.
  • Track this under kernel maintenance if no exposed service boundary exists.

Validation and detection

  • Inventory Linux kernel versions against the CVE affected-version list.
  • Confirm whether the sp5100_tco watchdog driver is present or loaded.
  • Verify installed kernels include one of the referenced stable fix commits.
  • Review vendor advisories for distro-specific package names and backports.
Prepared
Confidence
medium
Sources
6

Public sources used

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-50110 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb4c0f1600df43245c8c3425dbd9426fdfba6c4b2, 0578fff4aae5bce3f09875f58e68e9ffbab8daf5, 0578fff4aae5bce3f09875f58e68e9ffbab8daf5, 0578fff4aae5bce3f09875f58e68e9ffbab8daf5, 15b5d74600b98adf396d416ed59e0d43726f2671unaffected
LinuxLinux5.18, 0, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.