CVE-2022-49957
kcm: fix strp_init() order and cleanup
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
kcm: fix strp_init() order and cleanup
In the Linux kernel, the following vulnerability has been resolved: kcm: fix strp_init() order and cleanup strp_init() is called just a few lines above this csk->sk_user_data check, it also initializes strp->work etc., therefore, it is unnecessary to call strp_done() to cancel the freshly initialized work. And if sk_user_data is already used by KCM, psock->strp should not be touched, particularly strp->work state, so we need to move strp_init() after the csk->sk_user_data check. This also makes a lockdep warning reported by syzbot go away.
Reserved 2025-06-18 | Published 2025-06-18 | Updated 2025-06-18 | Assigner Linuxgit.kernel.org/...c/473f394953216614087f4179e55cdf0cf616a13b
git.kernel.org/...c/a8a0c321319ad64a5427d6172cd9c23b4d6ca1e8
git.kernel.org/...c/0946ff31d1a8778787bf6708beb20f38715267cc
git.kernel.org/...c/1b6666964ca1de93a7bf06e122bcf3616dbd33a9
git.kernel.org/...c/55fb8c3baa8071c5d533a9ad48624e44e2a04ef5
git.kernel.org/...c/f865976baa85915c7672f351b74d5974b93215f6
git.kernel.org/...c/8fc29ff3910f3af08a7c40a75d436b5720efe2bf
Support options
