CVE-2023-52502: net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()
In the Linux kernel, the following vulnerability has been resolved:
net: nfc: fix races in nfcllcpsockget() and nfcllcpsockgetsn()
Sili Luo reported a race in nfcllcpsockget(), leading to UAF.
Getting a reference on the socket found in a lookup while holding a lock should happen before releasing the lock.
nfcllcpsockgetsn() has a similar problem.
Finally nfcllcprecvsnl() needs to make sure the socket found by nfcllcpsockfromsn() does not disappear.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
Event History
Frequently Asked Questions
What is the severity of CVE-2023-52502?
CVE-2023-52502 is classified as a medium severity vulnerability due to potential use-after-free (UAF) issues.
How do I fix CVE-2023-52502?
You can fix CVE-2023-52502 by updating your Linux kernel to one of the patched versions: 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.128-1, or 6.12.12-1.
What components are affected by CVE-2023-52502?
CVE-2023-52502 specifically affects the Linux kernel networking stack related to NFC sockets.
Who reported CVE-2023-52502 and what issue did it address?
CVE-2023-52502 was reported by Sili Luo and addresses a race condition in the nfc_llcp_sock_get() leading to a use-after-free vulnerability.
Is CVE-2023-52502 present in all Linux kernel versions?
No, CVE-2023-52502 is not present in all versions; it has been resolved in specific patched versions of the Linux kernel.