CVE-2022-49779
kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Weakness
Affected products
- affected 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 – < 7b0007b28dd970176f2e297c06ae63eea2447127
- affected 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 – < 7d606ae1abcc3eab5408e42444d789dc7def51b8
- affected 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 – < c49cc2c059b503e962c2f13a806c105f9b757df4
- affected 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 – < 55788ebbe8b365b4375bd56b4ba7db79d393a370
- affected 0bc11ed5ab60c135aa764a62c02cd5ea68289de4 – < 5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebb
- affected 5.4
- unaffected < 5.4
- unaffected 5.4.225 – ≤ 5.4.*
- unaffected 5.10.156 – ≤ 5.10.*
- unaffected 5.15.80 – ≤ 5.15.*
- unaffected 6.0.10 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References (5)
- https://git.kernel.org/stable/c/7b0007b28dd970176f2e297c06ae63eea2447127 (opens in a new tab)
- https://git.kernel.org/stable/c/7d606ae1abcc3eab5408e42444d789dc7def51b8 (opens in a new tab)
- https://git.kernel.org/stable/c/c49cc2c059b503e962c2f13a806c105f9b757df4 (opens in a new tab)
- https://git.kernel.org/stable/c/55788ebbe8b365b4375bd56b4ba7db79d393a370 (opens in a new tab)
- https://git.kernel.org/stable/c/5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebb (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-49779)Record last updated .