CVE-2023-53557: fprobe: Release rethook after the ftrace_ops is unregistered
In the Linux kernel, the following vulnerability has been resolved:
fprobe: Release rethook after the ftraceops is unregistered
While running bpf selftests it's possible to get following fault:
general protection fault, probably for non-canonical address \ 0x6b6b6b6b6b6b6b6b: 0000 [#1] PREEMPT SMP DEBUGPAGEALLOC NOPTI ... Call Trace: <TASK> fprobehandler+0xc1/0x270 ? pfxbpftestmodinit+0x10/0x10 ? pfxbpftestmodinit+0x10/0x10 ? bpffentrytest1+0x5/0x10 ? bpffentrytest1+0x5/0x10 ? bpftestmodinit+0x22/0x80 ? dooneinitcall+0x63/0x2e0 ? rcuiswatching+0xd/0x40 ? kmalloctrace+0xaf/0xc0 ? doinitmodule+0x60/0x250 ? dosysfinitmodule+0xac/0x120 ? dosyscall64+0x37/0x90 ? entrySYSCALL64afterhwframe+0x72/0xdc </TASK>
In unregisterfprobe function we can't release fp->rethook while it's possible there are some of its users still running on another cpu.
Moving rethookfree call after fp->ops is unregistered with unregisterftracefunction call.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-53557?
CVE-2023-53557 is classified as a moderate severity vulnerability in the Linux kernel.
What does CVE-2023-53557 affect?
CVE-2023-53557 affects the Linux Kernel, specifically related to the fprobe functionality and ftrace operations.
How do I fix CVE-2023-53557?
To mitigate CVE-2023-53557, update your Linux kernel to the latest version where the vulnerability has been resolved.
What are the potential impacts of CVE-2023-53557?
Exploitation of CVE-2023-53557 could lead to a general protection fault, possibly affecting system stability.
Is there a workaround for CVE-2023-53557?
There are no known workarounds for CVE-2023-53557; applying the appropriate kernel update is recommended.