# CVE-2022-49779: kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case

Status: published. Published: 2025-05-01. Updated: 2026-11-05.

In the Linux kernel, the following vulnerability has been resolved:

kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case

In __unregister_kprobe_top(), if the currently unregistered probe has
post_handler but other child probes of the aggrprobe do not have
post_handler, the post_handler of the aggrprobe is cleared. If this is
a ftrace-based probe, there is a problem. In later calls to
disarm_kprobe(), we will use kprobe_ftrace_ops because post_handler is
NULL. But we're armed with kprobe_ipmodify_ops. This triggers a WARN in
__disarm_kprobe_ftrace() and may even cause use-after-free:

  Failed to disarm kprobe-ftrace at kernel_clone+0x0/0x3c0 (error -2)
  WARNING: CPU: 5 PID: 137 at kernel/kprobes.c:1135 __disarm_kprobe_ftrace.isra.21+0xcf/0xe0
  Modules linked in: testKprobe_007(-)
  CPU: 5 PID: 137 Comm: rmmod Not tainted 6.1.0-rc4-dirty #18
  [...]
  Call Trace:
   <TASK>
   __disable_kprobe+0xcd/0xe0
   __unregister_kprobe_top+0x12/0x150
   ? mutex_lock+0xe/0x30
   unregister_kprobes.part.23+0x31/0xa0
   unregister_kprobe+0x32/0x40
   __x64_sys_delete_module+0x15e/0x260
   ? do_user_addr_fault+0x2cd/0x6b0
   do_syscall_64+0x3a/0x90
   entry_SYSCALL_64_after_hwframe+0x63/0xcd
   [...]

For the kprobe-on-ftrace case, we keep the post_handler setting to
identify this aggrprobe armed with kprobe_ipmodify_ops. This way we
can disarm it correctly.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < 7b0007b28dd970176f2e297c06ae63eea2447127 (affected, git); ≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < 7d606ae1abcc3eab5408e42444d789dc7def51b8 (affected, git); ≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < c49cc2c059b503e962c2f13a806c105f9b757df4 (affected, git); ≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < 55788ebbe8b365b4375bd56b4ba7db79d393a370 (affected, git); ≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < 5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebb (affected, git). Source: CNA: Linux
- Linux / Linux: 5.4 (affected); ≥ 0; < 5.4 (unaffected, semver); ≥ 5.4.225; ≤ 5.4.* (unaffected, semver); ≥ 5.10.156; ≤ 5.10.* (unaffected, semver); ≥ 5.15.80; ≤ 5.15.* (unaffected, semver); ≥ 6.0.10; ≤ 6.0.* (unaffected, semver); ≥ 6.1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.22% as of 2026-11-05; percentile 12.68%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/7b0007b28dd970176f2e297c06ae63eea2447127 (CNA: Linux)

- https://git.kernel.org/stable/c/7d606ae1abcc3eab5408e42444d789dc7def51b8 (CNA: Linux)

- https://git.kernel.org/stable/c/c49cc2c059b503e962c2f13a806c105f9b757df4 (CNA: Linux)

- https://git.kernel.org/stable/c/55788ebbe8b365b4375bd56b4ba7db79d393a370 (CNA: Linux)

- https://git.kernel.org/stable/c/5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebb (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2022-49779; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2022-49779; retrieved 2026-11-05; source updated Not reported

Revision: 55da73d8f1ada4cc1fec48680ae4bb9fee419eaf8ee09ad8c5487a79c07454a6

Canonical: https://y2.dev/cve/CVE-2022-49779

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.