Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2024-53140

netlink: terminate outstanding dump on socket close

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 4.5, 4.9, 4.19.325, 5.4.287, 5.10.231, and 4 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From ed5d7788a934a4b6d6d025e948ed4da496b4f12e · fixed in 114a61d8d94ae3a43b82446cf737fd757021b834; From ed5d7788a934a4b6d6d025e948ed4da496b4f12e · fixed in 598c956b62699c3753929602560d8df322e60559; From ed5d7788a934a4b6d6d025e948ed4da496b4f12e · fixed in 6e3f2c512d2b7dbd247485b1dd9e43e4210a18f4; From ed5d7788a934a4b6d6d025e948ed4da496b4f12e · fixed in d2fab3d66cc16cfb9e3ea1772abe6b79b71fa603; From ed5d7788a934a4b6d6d025e948ed4da496b4f12e · fixed in 4e87a52133284afbd40fb522dbf96e258af52a98; From ed5d7788a934a4b6d6d025e948ed4da496b4f12e · fixed in bbc769d2fa1b8b368c5fbe013b5b096afa3c05ca; From ed5d7788a934a4b6d6d025e948ed4da496b4f12e · fixed in 176c41b3ca9281a9736b67c6121b03dbf0c8c08f; From ed5d7788a934a4b6d6d025e948ed4da496b4f12e · fixed in 1904fb9ebf911441f90a68e96b22aa73e4410505; From 4.4.38 · fixed in 4.5; From 4.8.14 · fixed in 4.9

  • Linux Linux

    4.9

  • KernelLinux

    From 4.9.0 · fixed in 4.19.325; From 4.20.0 · fixed in 5.4.287; From 5.5.0 · fixed in 5.10.231; From 5.11.0 · fixed in 5.15.174; From 5.16.0 · fixed in 6.1.119; From 6.2.0 · fixed in 6.6.63; From 6.7.0 · fixed in 6.11.10

References 8

git.kernel.org