CVE-2022-50075

published 18 Jun 2025 · updated 11 May 2026

tracing/eprobes: Have event probes be consistent with kprobes and uprobes

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 47cc883f21fa3bcf24891b4b455f4cd461ce2d6e, Kernel 6a832ec3d680b3a4f4fad5752672827d71bae501 and Kernel b489aca082a23033a3d8355cfb0032f0e2523440.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.15, >=7491e2c442781a1860181adb5ab472a52075f393 <47cc883f21fa3bcf24891b4b455f4cd461ce2d6e, >=7491e2c442781a1860181adb5ab472a52075f393 <6a832ec3d680b3a4f4fad5752672827d71bae501, >=7491e2c442781a1860181adb5ab472a52075f393 <b489aca082a23033a3d8355cfb0032f0e252344047cc883f21fa3bcf24891b4b455f4cd461ce2d6e, 6a832ec3d680b3a4f4fad5752672827d71bae501, b489aca082a23033a3d8355cfb0032f0e2523440

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-50075 severity on Zeptric[![CVE-2022-50075](https://zeptric.io/badge/cve/CVE-2022-50075.svg)](https://zeptric.io/cve/CVE-2022-50075)