Security readout for executives and security teams
Plain-English summary
This CVE concerns a resource leak in the Linux kernel turbostat tool. If parsing input fails, the tool can return without closing an open file pointer. The provided sources do not show privilege escalation, remote attack, data exposure, CVSS scoring, or active exploitation.
Executive priority
Treat this as low operational urgency based on the provided evidence. Track it through routine Linux update management, and escalate only if a vendor advisory assigns higher impact for your deployed distribution.
Technical view
The issue is in tools/power/x86/turbostat/turbostat.c. A failed fscanf path leaked fp before returning. The kernel stable fix closes the file before the early return. The finding was detected by cppcheck static analysis.
Likely exposure
Exposure is likely limited to environments shipping or using affected Linux kernel source/tooling versions that include the vulnerable turbostat code path. The source bundle lists Linux 5.19-era affected version data and stable kernel references.
Exploitation context
CISA KEV status is false in the source bundle. No cited source reports active exploitation or weaponized use. The available evidence points to a local tool resource-management bug, not a remotely exploitable service vulnerability.
Researcher notes
Evidence is narrow: no CVSS, CWE, exploit report, or detailed impact analysis is provided. The affected component is turbostat under Linux kernel power tools, and the fix addresses a file pointer leak on an error path.
Mitigation direction
- Apply Linux vendor updates that include the referenced stable fixes.
- For source builds, backport the referenced kernel stable commits.
- Check distribution advisories before making production kernel changes.
- Prioritize normal patch cadence unless vendor guidance raises severity.
Validation and detection
- Inventory systems or build trees using affected Linux kernel tooling versions.
- Confirm turbostat source includes fclose before the fscanf failure return.
- Compare local source against the referenced stable commits.
- Review vendor package changelogs for CVE-2022-50189 coverage.
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-2022-50189 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/2ebf6f5946817f33fb33e613e359229e98164eb3CVE reference, Linux
- https://git.kernel.org/stable/c/5e5fd36c58d6c820f7292ee492c3731c9a104a41CVE 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.