CVE-2022-50075: tracing/eprobes: Have event probes be consistent with kprobes and uprobes

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-06-18 · updated 2026-06-17
Weakness: CWE-476

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.

Affected products

Linux kernel: from 5.15 before 5.15.63; from 5.16 before 5.19.4; 6.0-rc1 — fixed in 5.15.63, 5.19.4

How to fix

Upgrade to a fixed version: Linux kernel 5.15.63, 5.19.4. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2022-50075 or the next vulnerability affects your stack