<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T22:10:00.449780+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2022-50266</id>
    <title>CVE-2022-50266 — kprobes: Fix check for probe enabled in kill_kprobe()</title>
    <updated>2026-09-30T22:10:01.992314+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>kprobes: Fix check for probe enabled in kill_kprobe()</p>
<p>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.</p>
<p>The disarm_kprobe_ftrace() call introduced by commit:</p>
<p>0cb2f1372baa ("kprobes: Fix NULL pointer dereference at kprobe_ftrace_handler")</p>
<p>to fix the NULL pointer reference problem. When the probe is enabled, if
we do not disarm it, this problem still exists.</p>
<p>Fix it by putting the probe enabled check before setting the
KPROBE_FLAG_GONE flag.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-50266"/>
  </entry>
</feed>
