LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50142: intel_th: msu: Fix vmalloced buffers

In the Linux kernel, the following vulnerability has been resolved: intel_th: msu: Fix vmalloced buffers After commit f5ff79fddf0e ("dma-mapping: remove CONFIG_DMA_REMAP") there's a chance of DMA buffer getting allocated via vmalloc(), which messes up the mmapping code: > RIP: msc_mmap_fault [intel_th_msu] > Call Trace: > <TASK> > __do_fault > do_fault ... Fix this by accounting for vmalloc possibility.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50142 is a Linux kernel bug in the Intel Trace Hub MSU driver. A memory-mapping path could mishandle DMA buffers allocated through vmalloc, leading to kernel fault behavior. The public record does not provide CVSS, impact severity, or evidence of active exploitation.

Executive priority

Treat this as a kernel maintenance item unless your environment uses Intel Trace Hub MSU on affected Linux kernels. With no CVSS, KEV listing, or exploit evidence, urgency depends on local driver exposure and vendor patch availability.

Technical view

The issue is in intel_th_msu. After removal of CONFIG_DMA_REMAP, DMA buffers may be vmalloc-backed, and msc_mmap_fault did not account for that possibility. The fix updates the mmap fault handling for vmalloced buffers. Public details show crash context, not a full exploit path.

Likely exposure

Exposure appears limited to Linux kernels in the affected version ranges where the Intel Trace Hub MSU driver is present or used. The source bundle does not identify specific distributions, default configurations, remote exposure, or required privileges.

Exploitation context

CISA KEV is false in the supplied data, and the sources do not cite active exploitation. The available description shows a kernel fault scenario, but not attacker control, exploitation prerequisites, or weaponized public exploit activity.

Researcher notes

Key unknowns are severity, privilege requirements, reachable attack surface, and distribution-specific affected builds. The affected-version data is broad and commit-oriented, so validation should rely on vendor backports rather than version strings alone.

Mitigation direction

  • Apply Linux kernel updates from your distribution or vendor that include the referenced stable fixes.
  • Verify whether your running kernel branch contains the relevant upstream stable commit.
  • Track vendor advisories because the source bundle does not name distribution-specific fixed packages.
  • Assess whether Intel Trace Hub MSU is needed on exposed systems before changing driver availability.

Validation and detection

  • Inventory Linux kernel versions and compare them with vendor fixed-release guidance.
  • Check whether the intel_th_msu driver is built, loaded, or used on relevant systems.
  • Confirm patched kernels include one of the referenced stable commits or equivalent backports.
  • Review kernel logs for msc_mmap_fault or intel_th_msu crash signatures.
Prepared
Confidence
medium
Sources
8

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-50142 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
7Source 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
LinuxLinuxba39bd8306057fb343dfb75d93a76d824b625236, ba39bd8306057fb343dfb75d93a76d824b625236, ba39bd8306057fb343dfb75d93a76d824b625236, ba39bd8306057fb343dfb75d93a76d824b625236, ba39bd8306057fb343dfb75d93a76d824b625236, ba39bd8306057fb343dfb75d93a76d824b625236unaffected
LinuxLinux5.2, 0, 5.4.211, 5.10.137, 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.