udp: fix race between close() and udp_abort()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5d77dca82839ef016a93ad7acd7058b14d967752 · < 65310b0aff86980a011c7c7bfa487a333d4ca241| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
udp: fix race between close() and udp_abort()
Kaustubh reported and diagnosed a panic in udp_lib_lookup(). The root cause is udp_abort() racing with close(). Both racing functions acquire the socket lock, but udp{v6}_destroy_sock() release it before performing destructive actions.
We can't easily extend the socket lock scope to avoid the race, instead use the SOCK_DEAD flag to prevent udp_abort from doing any action when the critical race happens.
Diagnosed-and-tested-by: Kaustubh Pandey <kapandey@codeaurora.org>
From the CVE record · Linux
A race between close() and udp_abort() in the Linux kernel can cause a panic in udp_lib_lookup(). The input does not specify how an attacker could trigger the race or whether network access, authentication, or user interaction is required.
Anyone running the Linux kernel should check whether their version is affected; affected versions are not specified in the input.