CVE-2022-50075

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.

The following products are affected by CVE-2022-50075 vulnerability.

Here, you will find a curated list of external links that provide in-depth information to CVE-2022-50075.

URL	Resource
https://git.kernel.org/stable/c/47cc883f21fa3bcf24891b4b455f4cd461ce2d6e
https://git.kernel.org/stable/c/6a832ec3d680b3a4f4fad5752672827d71bae501
https://git.kernel.org/stable/c/b489aca082a23033a3d8355cfb0032f0e2523440
https://lore.kernel.org/linux-cve-announce/2025061854-CVE-2022-50075-f791@gregkh/T
https://nvd.nist.gov/vuln/detail/CVE-2022-50075
https://www.cve.org/CVERecord?id=CVE-2022-50075