CVE-2022-50142: intel_th: msu: Fix vmalloced buffers
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0ed72c6bc632cbf8d979ac60f982ff84b7bb610a, 4914c50670b6a531e2cb17cd984cc565b4681312, 566887bad7ff2297d6b3f9659c702ba075f3d62d.
Low priority for now. Upgrade to Linux Linux 0ed72c6bc632cbf8d979ac60f982ff84b7bb610a, 4914c50670b6a531e2cb17cd984cc565b4681312, 566887bad7ff2297d6b3f9659c702ba075f3d62d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 18, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.2 and later · before 5.4.211
- linux linux kernel5.5 and later · before 5.10.137
- linux linux kernel5.11 and later · before 5.15.61
- linux linux kernel5.16 and later · before 5.18.18
- linux linux kernel5.19 and later · before 5.19.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.2affected
- ba39bd8306057fb343dfb75d93a76d824b625236 and later · before b5d924cb4c7b952eaa61622f14427723a78137a3affected · git
- ba39bd8306057fb343dfb75d93a76d824b625236 and later · before 6ae2881c1d1fa0e33f4763b7c786f8ef05a9c828affected · git
- ba39bd8306057fb343dfb75d93a76d824b625236 and later · before 566887bad7ff2297d6b3f9659c702ba075f3d62daffected · git
- ba39bd8306057fb343dfb75d93a76d824b625236 and later · before 0ed72c6bc632cbf8d979ac60f982ff84b7bb610aaffected · git
- ba39bd8306057fb343dfb75d93a76d824b625236 and later · before 4914c50670b6a531e2cb17cd984cc565b4681312affected · git
- ba39bd8306057fb343dfb75d93a76d824b625236 and later · before ac12ad3ccf6d386e64a9d6a890595a2509d24eddaffected · git
- before 5.2not affected · semver
- 5.4.211 and later · up to and including 5.4.*not affected · semver
- 5.10.137 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.2-1 | 6.0.2-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50134Jun 18, 2025 · RDMA/hfi1: fix potential memory leak in setup_base_ctxt()22Monitor
- ← EarlierCVE-2022-50135Jun 18, 2025 · RDMA/rxe: Fix BUG: KASAN: null-ptr-deref in rxe_qp_do_cleanup22Monitor
- Later →CVE-2022-50143Jun 18, 2025 · intel_th: Fix a resource leak in an error handling path22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0ed72c6bc632cbf8d979ac60f982ff84b7bb610a | Vendor (CNA) |
| Linux Linux | 4914c50670b6a531e2cb17cd984cc565b4681312 | Vendor (CNA) |
| Linux Linux | 566887bad7ff2297d6b3f9659c702ba075f3d62d | Vendor (CNA) |
| Linux Linux | 6ae2881c1d1fa0e33f4763b7c786f8ef05a9c828 | Vendor (CNA) |
| Linux Linux | ac12ad3ccf6d386e64a9d6a890595a2509d24edd | Vendor (CNA) |
| Linux Linux | b5d924cb4c7b952eaa61622f14427723a78137a3 | Vendor (CNA) |
| debian:linux | 6.0.2-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/4914c50670b6a531e2cb17cd984cc565b4681312
- git.kernel.org/stable/c/566887bad7ff2297d6b3f9659c702ba075f3d62d
- git.kernel.org/stable/c/6ae2881c1d1fa0e33f4763b7c786f8ef05a9c828
- git.kernel.org/stable/c/ac12ad3ccf6d386e64a9d6a890595a2509d24edd
- git.kernel.org/stable/c/b5d924cb4c7b952eaa61622f14427723a78137a3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.