tracing/eprobes: Have event probes be consistent with kprobes and uprobes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.15.635.19.46.0In 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.
From the CVE record · Linux
The Linux kernel's event probes can trigger a NULL pointer dereference when a probe uses an "@" symbol. An attacker able to configure such a probe could cause a kernel crash; the input does not specify authentication requirements.
Engineers running Linux kernels with tracing event probes should check their deployments; affected versions are not specified.