linux: In the Linux kernel, the following vulnerability has been resolved: tracing/eprobes: Have event probes be consistent...
CVE-2022-50075 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50075, released June 18, 2025. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| linux · Debian 12.15 (bookworm) | 6.0.2-1 | DEBIAN-CVE-2022-50075 | Jun 18, 2025 |
| linux · Debian 13.5 (trixie) | 6.0.2-1 | DEBIAN-CVE-2022-50075 | Jun 18, 2025 |
| linux · Debian 14 | 6.0.2-1 | DEBIAN-CVE-2022-50075 | Jun 18, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.