CVE-2022-49779
kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < 7b0007b28dd970176f2e297c06ae63eea2447127 (affected, git) ≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < 7d606ae1abcc3eab5408e42444d789dc7def51b8 (affected, git) ≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < c49cc2c059b503e962c2f13a806c105f9b757df4 (affected, git) ≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < 55788ebbe8b365b4375bd56b4ba7db79d393a370 (affected, git) ≥ 0bc11ed5ab60c135aa764a62c02cd5ea68289de4; < 5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebb (affected, git) Other versions: unaffected |
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) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/7b0007b28dd970176f2e297c06ae63eea2447127CNA: Linux
- https://git.kernel.org/stable/c/7d606ae1abcc3eab5408e42444d789dc7def51b8CNA: Linux
- https://git.kernel.org/stable/c/c49cc2c059b503e962c2f13a806c105f9b757df4CNA: Linux
- https://git.kernel.org/stable/c/55788ebbe8b365b4375bd56b4ba7db79d393a370CNA: Linux
- https://git.kernel.org/stable/c/5dd7caf0bdc5d0bae7cf9776b4d739fb09bd5ebbCNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.