nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a69f32af86e389dd232b1bb2269e202c1bfcc60f · < 650bdd8fdfab64a09ee474150313dbc48c374795| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc()
A race condition exists in the NFC LLCP connection state machine where the connection acceptance packet (CC) can be processed concurrently with socket release. This can lead to a use-after-free of the socket object.
When nfc_llcp_recv_cc() moves the socket from the connecting_sockets list to the sockets list, it does so without holding the socket lock. If llcp_sock_release() is executing concurrently, it might have already unlinked the socket and dropped its references, which can result in nfc_llcp_recv_cc() linking a freed socket into the live list.
Fix this by holding lock_sock() during the state transition and list movement in nfc_llcp_recv_cc(). After acquiring the lock, check if the socket is still hashed to ensure it hasn't already been unlinked and marked for destruction by the release path. This aligns the locking pattern with recv_hdlc() and recv_disc().
From the CVE record · Linux
A race in the Linux kernel’s NFC LLCP connection state machine can cause a socket use-after-free. It occurs when a connection acceptance packet is processed concurrently with socket release. The input does not specify attacker access, authentication requirements, or user interaction.
Engineers running Linux kernels with NFC LLCP should check their exposure; affected versions are not specified.