diff options
| author | Petr Pavlu <petr.pavlu@suse.com> | 2026-08-06 11:10:16 +0200 |
|---|---|---|
| committer | Petr Pavlu <petr.pavlu@suse.com> | 2026-08-06 13:29:03 +0200 |
| commit | 5eecb11b543f9f417bcf0dea239ff99c6af65dbd (patch) | |
| tree | e6cf286786eb85920089cff48590ed0ddfc87886 /scripts/patch-kernel | |
| parent | d258ed8a86bb46bbbbc84fb914478259a1e694a4 (diff) | |
| download | linux-5eecb11b543f9f417bcf0dea239ff99c6af65dbd.tar.gz linux-5eecb11b543f9f417bcf0dea239ff99c6af65dbd.zip | |
module/dups: Fix use-after-free in kmod_dup_req lifetime handling
The kmod dups code uses RCU to ensure that a kmod_dup_req instance is freed
only after it is no longer referenced. When releasing an instance, the
kmod_dup_request_delete() function removes the kmod_dup_req from the
dup_kmod_reqs list, waits via synchronize_rcu() and finally frees it.
However, this doesn't work correctly because parallel users referencing the
instance in kmod_dup_request_exists_wait() don't enter an RCU read-side
critical section. This can result in a use-after-free.
The kmod_dup_request_exists_wait() function may need to hold a valid
reference to a kmod_dup_req instance across a blocking wait until the
corresponding modprobe command completes. This makes it unsuitable for RCU.
Fix the issue by changing the lifecycle management of kmod_dup_req to use
reference counting.
Fixes: 8660484ed1cf ("module: add debugging auto-load duplicate module support")
Reviewed-by: Aaron Tomlin <atomlin@atomlin.com>
Signed-off-by: Petr Pavlu <petr.pavlu@suse.com>
Diffstat (limited to 'scripts/patch-kernel')
0 files changed, 0 insertions, 0 deletions
