First published: Wed Dec 04 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: netlink: terminate outstanding dump on socket close Netlink supports iterative dumping of data. It provides the families the following ops: - start - (optional) kicks off the dumping process - dump - actual dump helper, keeps getting called until it returns 0 - done - (optional) pairs with .start, can be used for cleanup The whole process is asynchronous and the repeated calls to .dump don't actually happen in a tight loop, but rather are triggered in response to recvmsg() on the socket. This gives the user full control over the dump, but also means that the user can close the socket without getting to the end of the dump. To make sure .start is always paired with .done we check if there is an ongoing dump before freeing the socket, and if so call .done. The complication is that sockets can get freed from BH and .done is allowed to sleep. So we use a workqueue to defer the call, when needed. Unfortunately this does not work correctly. What we defer is not the cleanup but rather releasing a reference on the socket. We have no guarantee that we own the last reference, if someone else holds the socket they may release it in BH and we're back to square one. The whole dance, however, appears to be unnecessary. Only the user can interact with dumps, so we can clean up when socket is closed. And close always happens in process context. Some async code may still access the socket after close, queue notification skbs to it etc. but no dumps can start, end or otherwise make progress. Delete the workqueue and flush the dump state directly from the release handler. Note that further cleanup is possible in -next, for instance we now always call .done before releasing the main module reference, so dump doesn't have to take a reference of its own.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=4.4.38<4.5 | |
Linux Kernel | >=4.8.14<4.9 | |
Linux Kernel | >=4.9<6.1.119 | |
Linux Kernel | >=6.2<6.6.63 | |
Linux Kernel | >=6.7<6.11.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-53140 has a medium severity level due to the potential for denial of service through improper handling of netlink sockets.
To fix CVE-2024-53140, upgrade the Linux kernel to at least version 4.4.39, 4.8.14, 4.9.246, 6.1.120, 6.2.64, or a later version.
CVE-2024-53140 affects Linux kernel versions from 4.4.38 up to 4.5, 4.8.14 up to 4.9, 4.9 to 6.1.119, 6.2 to 6.6.63, and 6.7 to 6.11.10.
The impact of CVE-2024-53140 could lead to a denial of service as it allows an attacker to terminate outstanding dump processes on socket closure.
Currently, no specific workaround is recommended for CVE-2024-53140 other than applying the kernel update.