Kernel crash via vmalloc-backed DMA buffer mapping
Published Jun 18, 2025 · Updated May 11, 2026
Memory-mapping flaw in affected Linux kernel releases allows local users to crash the kernel through an Intel Trace Hub MSU buffer mapping. The msc_mmap_fault path can receive a DMA buffer allocated through vmalloc but handles its address as ordinary directly mapped memory rather than translating the vmalloc page. Triggering the fault requires local access to map an Intel Trace Hub MSU buffer; the published failure trace demonstrates a kernel crash.
Summary
What happened
Memory-mapping flaw in affected Linux kernel releases allows local users to crash the kernel through an Intel Trace Hub MSU buffer mapping. The msc_mmap_fault path can receive a DMA buffer allocated through vmalloc but handles its address as ordinary directly mapped memory rather than translating the vmalloc page. Triggering the fault requires local access to map an Intel Trace Hub MSU buffer; the published failure trace demonstrates a kernel crash.
The record
- CVE
- CVE-2022-50142
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.2
- Affected versionversion=ba39bd8306057fb343dfb75d93a76d824b625236 <0ed72c6bc632cbf8d979ac60f982ff84b7bb610a
- Affected versionversion=ba39bd8306057fb343dfb75d93a76d824b625236 <4914c50670b6a531e2cb17cd984cc565b4681312
- Affected versionversion=ba39bd8306057fb343dfb75d93a76d824b625236 <566887bad7ff2297d6b3f9659c702ba075f3d62d
- Affected versionversion=ba39bd8306057fb343dfb75d93a76d824b625236 <6ae2881c1d1fa0e33f4763b7c786f8ef05a9c828
- Affected versionversion=ba39bd8306057fb343dfb75d93a76d824b625236 <ac12ad3ccf6d386e64a9d6a890595a2509d24edd
- Affected versionversion=ba39bd8306057fb343dfb75d93a76d824b625236 <b5d924cb4c7b952eaa61622f14427723a78137a3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo