tracing: Fix race where eprobes can be called before the event
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.806.0.106.1In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix race where eprobes can be called before the event
The flag that tells the event to call its triggers after reading the event is set for eprobes after the eprobe is enabled. This leads to a race where the eprobe may be triggered at the beginning of the event where the record information is NULL. The eprobe then dereferences the NULL record causing a NULL kernel pointer bug.
Test for a NULL record to keep this from happening.
From the CVE record · Linux
A race in Linux kernel tracing can trigger an eprobe before its event record is available. If that happens, the eprobe can dereference a NULL record and cause a kernel NULL pointer bug. The input does not specify whether triggering this requires local access, authentication, or user interaction.
Anyone running the Linux kernel should check whether their version is affected; affected versions are not specified.