CVE-2022-50075 tracing/eprobes: Have event probes be consistent with kprobes and uprobes
A NULL pointer dereference in Linux kernel event probes allows local attackers to cause a system crash by using specific symbols.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-50075?
CVE-2022-50075 is a medium-severity vulnerability in Linux kernel, published on 18 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
In the Linux kernel, the following vulnerability has been resolved:
tracing/eprobes: Have event probes be consistent with kprobes and uprobes
Currently, if a symbol "@" is attempted to be used with an event probe (eprobes), it will cause a NULL pointer dereference crash.
Both kprobes and uprobes can reference data other than the main registers. Such as immediate address, symbols and the current task name. Have eprobes do the same thing.
For "comm", if "comm" is used and the event being attached to does not have the "comm" field, then make it the "$comm" that kprobes has. This is consistent to the way histograms and filters work.
Weakness: CWE-476
Which versions are affected by CVE-2022-50075?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2022-50075?
Apply the vendor's patch.
Is CVE-2022-50075 being exploited?
There is no known exploitation of CVE-2022-50075 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as DEBIAN-CVE-2022-50075, GHSA-xpmp-pq5g-mgh6, UBUNTU-CVE-2022-50075.