CVE-2022-50143: intel_th: Fix a resource leak in an error handling path
In the Linux kernel, the following vulnerability has been resolved:
intel_th: Fix a resource leak in an error handling path
If an error occurs after calling 'pci_alloc_irq_vectors()',
'pci_free_irq_vectors()' must be called as already done in the remove
function.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel resource leak in the Intel Trace Hub driver error path. If setup fails after IRQ vectors are allocated, the kernel failed to free them. The provided sources do not show active exploitation, CVSS, or broad impact details, so business urgency should be driven by normal kernel patch management.
Executive priority
Treat this as routine kernel maintenance unless internal exposure analysis finds sensitive systems on affected kernels. There is no provided evidence of exploitation or critical impact, but kernel fixes should still be absorbed through standard patch cycles.
Technical view
The fix adds cleanup after pci_alloc_irq_vectors() when later initialization fails in intel_th. The remove path already freed IRQ vectors; the vulnerable error path did not. Evidence only identifies Linux kernel affected versions and stable-tree fixes, without exploitability, privilege, or attack-vector details.
Likely exposure
Systems running affected Linux kernel builds with the Intel Trace Hub driver code present may be exposed. The source bundle lists Linux kernel versions and stable commit fixes, but does not map distribution packages or configurations.
Exploitation context
The provided sources do not indicate active exploitation, and the CVE is not marked KEV. No exploit method, attack vector, or required privileges are provided, so exploitation likelihood cannot be reliably assessed from this bundle.
Researcher notes
The weakness is a missing pci_free_irq_vectors() call on a probe error path after pci_alloc_irq_vectors(). The source bundle lacks CVSS, CWE, distro package mapping, and practical exploitability details, so conclusions should remain conservative.
Mitigation direction
Update affected Linux kernels through the normal distribution or vendor kernel channel.
Confirm the installed kernel includes one of the referenced stable fixes.
For custom kernels, backport the upstream stable patch for the relevant branch.
Reboot into the updated kernel after patching.
Monitor Linux distribution advisories for package-specific guidance.
Validation and detection
Inventory Linux kernel versions across servers and endpoints.
Check vendor changelogs for CVE-2022-50143 or the referenced commit IDs.
Verify the running kernel, not only the installed package, is updated.
Review whether Intel Trace Hub support is built or loaded where relevant.
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-50143 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.
0CVSS vectors
3Timeline events
0ADP providers
7Source links
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.
Jun 18, 2025, 11:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.