Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.15, < 5.15.63 |
Related Weaknesses (CWE)
References
- https://git.kernel.org/stable/c/47cc883f21fa3bcf24891b4b455f4cd461ce2d6ePatch
- https://git.kernel.org/stable/c/6a832ec3d680b3a4f4fad5752672827d71bae501Patch
- https://git.kernel.org/stable/c/b489aca082a23033a3d8355cfb0032f0e2523440Patch
FAQ
What is CVE-2022-50075?
CVE-2022-50075 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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 ...
How severe is CVE-2022-50075?
CVE-2022-50075 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-50075?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.