CVE-2024-53140 — netlink: terminate outstanding dump on socket close
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ ed5d7788a934a4b6d6d025e948ed4da496b4f12e and < 4e87a52133284afbd40fb522dbf96e258af52a98version 4.9≥ 4.8.14 and < 4.9≥ 4.4.38 and < 4.5version 25d9b4bb64ea964769087fc5ae09aee9c838d759version baaf0c65bc8ea9c7a404b09bc8cc3b8a1e4f18df≥ ed5d7788a934a4b6d6d025e948ed4da496b4f12e and < 1904fb9ebf911441f90a68e96b22aa73e4410505≥ ed5d7788a934a4b6d6d025e948ed4da496b4f12e and < 176c41b3ca9281a9736b67c6121b03dbf0c8c08f and 5 more≥ ed5d7788a934a4b6d6d025e948ed4da496b4f12e and < bbc769d2fa1b8b368c5fbe013b5b096afa3c05ca≥ ed5d7788a934a4b6d6d025e948ed4da496b4f12e and < d2fab3d66cc16cfb9e3ea1772abe6b79b71fa603≥ ed5d7788a934a4b6d6d025e948ed4da496b4f12e and < 6e3f2c512d2b7dbd247485b1dd9e43e4210a18f4≥ ed5d7788a934a4b6d6d025e948ed4da496b4f12e and < 598c956b62699c3753929602560d8df322e60559≥ ed5d7788a934a4b6d6d025e948ed4da496b4f12e and < 114a61d8d94ae3a43b82446cf737fd757021b834 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 4.4.38 and < 4.5≥ 6.7 and < 6.11.10≥ 6.2 and < 6.6.63≥ 4.9 and < 6.1.119≥ 4.8.14 and < 4.9 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2024
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
13 on the record
- git.kernel.org/stable/c/114a61d8d94ae3a43b82446cf737fd757021b834
- git.kernel.org/stable/c/bbc769d2fa1b8b368c5fbe013b5b096afa3c05ca
- git.kernel.org/stable/c/4e87a52133284afbd40fb522dbf96e258af52a98
- git.kernel.org/stable/c/176c41b3ca9281a9736b67c6121b03dbf0c8c08f
- git.kernel.org/stable/c/1904fb9ebf911441f90a68e96b22aa73e4410505
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- git.kernel.org/stable/c/6e3f2c512d2b7dbd247485b1dd9e43e4210a18f4
- git.kernel.org/stable/c/598c956b62699c3753929602560d8df322e60559
- git.kernel.org/stable/c/d2fab3d66cc16cfb9e3ea1772abe6b79b71fa603
- github.com/advisories/GHSA-pc3w-52r9-h2g7
- nvd.nist.gov/vuln/detail/CVE-2024-53140
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-53140 is "netlink: terminate outstanding dump on socket close", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.