CVE-2022-50266
Last modified
CVE-2022-50266 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: kprobes: Fix check for probe enabled in kill_kprobe() In kill_kprobe(), the check whether disarm_kprobe_ftrace() needs to be called always fails. This is because before that we set the KPROBE_FLAG_GONE flag for kprobe so that "!kprobe_disabled(p)" is always false. The disarm_kprobe_ftrace() call introduced by commit: 0cb2f1372baa ("kprobes: Fix NULL pointer dereference at kprobe_ftrace_handler") to fix the NULL pointer reference problem. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: kprobes: Fix check for probe enabled in kill_kprobe() In kill_kprobe(), the check whether disarm_kprobe_ftrace() needs to be called always fails. This is because before that we set the KPROBE_FLAG_GONE flag for kprobe so that "!kprobe_disabled(p)" is always false. The disarm_kprobe_ftrace() call introduced by commit: 0cb2f1372baa ("kprobes: Fix NULL pointer dereference at kprobe_ftrace_handler") to fix the NULL pointer reference problem. When the probe is enabled, if we do not disarm it, this problem still exists. Fix it by putting the probe enabled check before setting the KPROBE_FLAG_GONE flag.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.4.238, < 4.5 |
| Linux | Linux Kernel | >= 4.9.238, < 4.10 |
| Linux | Linux Kernel | >= 4.14.200, < 4.15 |
| Linux | Linux Kernel | >= 4.19.149, < 4.20 |
| Linux | Linux Kernel | >= 5.4.69, < 5.5 |
| Linux | Linux Kernel | >= 5.8.13, < 5.9 |
| Linux | Linux Kernel | >= 5.9.1, < 6.0.16 |
| Linux | Linux Kernel | >= 6.1, < 6.1.2 |
| Linux | Linux Kernel | 5.9 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-50266?
How severe is CVE-2022-50266?
How do I fix CVE-2022-50266?
Are you affected by CVE-2022-50266?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
