Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-50266kprobes: Fix check for probe enabled in kill_kprobe()

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50266, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 3031313eb3d549b7ad6f9fbcc52ba04412e3eb9e – < f20a067f13106565816b4b6a6b665b2088a63824
    • affected 3031313eb3d549b7ad6f9fbcc52ba04412e3eb9e – < c909985dd0c0f74b61e3f8f0e04bf8aa9c8b97c7
    • affected 3031313eb3d549b7ad6f9fbcc52ba04412e3eb9e – < 0c76ef3f26d5ef2ac2c21b47e7620cff35809fbb
    • affected 3c5f8d371b7fef3e3714c4a062c7f3b4aa41d122
    • affected 9b55d84deec88c02b053a819acf08a6d471dda02
    • affected 2295608b44c91df767a5c68027f9c9e52ecb28e7
    • affected ce7ff920092130f249b75f9fe177edb3362fefe8
    • affected 3995f7a60feceba6c8f762f4aff3184f90a1291d
    • affected 247c62ebdfae450bb76dd89cd4724df6be07df75
    • affected 4.4.238 – < 4.5
    • affected 4.9.238 – < 4.10
    • affected 4.14.200 – < 4.15
    • affected 4.19.149 – < 4.20
    • affected 5.4.69 – < 5.5
    • affected 5.8.13 – < 5.9
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50266 badge
[![CVE-2022-50266](https://cveledger.app/badge/CVE-2022-50266.svg)](https://cveledger.app/cve/CVE-2022-50266)

Record last updated .