Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() bt_sock_alloc() attaches allocated sk object to the provided sock object. If rfcomm_dlc_alloc() fails, we release the sk object, but leave the dangling pointer in the sock object, which may cause use-after-free. Fix this by swapping calls to bt_sock_alloc() and rfcomm_dlc_alloc().
Product status
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before ac3eaac4cf142a15fe67be747a682b1416efeb6e
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 6021ccc2471b7b95e29b7cfc7938e042bf56e281
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 32df687e129ef0f9afcbcc914f7c32deb28fd481
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 3945c799f12b8d1f49a3b48369ca494d981ac465
6.1.120 (semver)
6.6.66 (semver)
6.12.5 (semver)
6.13 (original_commit_for_fix)
References
git.kernel.org/...c/ac3eaac4cf142a15fe67be747a682b1416efeb6e
git.kernel.org/...c/6021ccc2471b7b95e29b7cfc7938e042bf56e281
git.kernel.org/...c/32df687e129ef0f9afcbcc914f7c32deb28fd481
git.kernel.org/...c/3945c799f12b8d1f49a3b48369ca494d981ac465
