CVE-2022-50266

kprobes: Fix check for probe enabled in kill_kprobe()

MEDIUM
5.5
CVSS Score
Published: September 15, 2025 at 02:21 PM UTC
Updated: June 17, 2026 at 05:23 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.14.200v ≥ 4.19.149v ≥ 4.4.238v ≥ 4.9.238v ≥ 5.4.69v ≥ 5.8.134.14.200 ≤ v < 4.154.19.149 ≤ v < 4.204.4.238 ≤ v < 4.54.9.238 ≤ v < 4.105.4.69 ≤ v < 5.55.8.13 ≤ v < 5.95.9 ≤ v < 6.0.165.9 ≤ v < 6.1.25.9 ≤ v < 6.25.9.1 ≤ v < 6.0.166.1 ≤ v < 6.1.22295608b44c91df767a5c68027f9c9e52ecb28e7247c62ebdfae450bb76dd89cd4724df6be07df753031313eb3d549b7ad6f9fbcc52ba04412e3eb9e3995f7a60feceba6c8f762f4aff3184f90a1291d3c5f8d371b7fef3e3714c4a062c7f3b4aa41d1224.14.2004.19.1494.4.2384.9.2385.4.695.8.135.95.9 rc75.9 rc89b55d84deec88c02b053a819acf08a6d471dda02ce7ff920092130f249b75f9fe177edb3362fefe8
Vendor states this is fixed in 0c76ef3f26d5ef2ac2c21b47e7620cff35809fbb (fixed)
Vendor states this is fixed in c909985dd0c0f74b61e3f8f0e04bf8aa9c8b97c7 (fixed)
Vendor states this is fixed in f20a067f13106565816b4b6a6b665b2088a63824 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.9 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

References (3)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0c76ef3f26d5ef2ac2c21b47e7620cff35809fbb
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c909985dd0c0f74b61e3f8f0e04bf8aa9c8b97c7
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f20a067f13106565816b4b6a6b665b2088a63824

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card