CVE-2025-68372
nbd: defer config put in recv_work
Reported by linux · Published December 24, 2025
In the Linux kernel, the following vulnerability has been resolved: nbd: defer config put in recv_work There is one uaf issue in recv_work when running NBD_CLEAR_SOCK and NBD_CMD_RECONFIGURE: nbd_genl_connect // conf_ref=2 (connect and recv_work A) nbd_open // conf_ref=3 recv_work A done // conf_ref=2 NBD_CLEAR_SOCK // conf_ref=1 nbd_genl_reconfigure // conf_ref=2 (trigger recv_work B) close nbd // conf_ref=1 recv_work B config_put // conf_ref=0 atomic_dec(&config->recv_threads); -> UAF Or only running NBD_CLEAR_SOCK: nbd_genl_connect // conf_ref=2 nbd_open // conf_ref=3 NBD_CLEAR_SOCK // conf_ref=2 close nbd nbd_release config_put // conf_ref=1 recv_work config_put // conf_ref=0 atomic_dec(&config->recv_threads); -> UAF Commit 87aac3a80af5 ("nbd: call nbd_config_put() before notifying the waiter") moved nbd_config_put() to run before waking up the waiter in recv_work, in order to ensure that nbd_start_device_ioctl() would not be woken up while nbd->task_recv was still uncleared. However, in nbd_start_device_ioctl(), after being woken up it explicitly calls flush_workqueue() to make sure all current works are finished. Therefore, there is no need to move the config put ahead of the wakeup. Move nbd_config_put() to the end of recv_work, so that the reference is held for the whole lifetime of the worker thread. This makes sure the config cannot be freed while recv_work is still running, even if clear + reconfigure interleave. In addition, we don't need to worry about recv_work dropping the last nbd_put (which causes deadlock): path A (netlink with NBD_CFLAG_DESTROY_ON_DISCONNECT): connect // nbd_refs=1 (trigger recv_work) open nbd // nbd_refs=2 NBD_CLEAR_SOCK close nbd nbd_release nbd_disconnect_and_put flush_workqueue // recv_work done nbd_config_put nbd_put // nbd_refs=1 nbd_put // nbd_refs=0 queue_work path B (netlink without NBD_CFLAG_DESTROY_ON_DISCONNECT): connect // nbd_refs=2 (trigger recv_work) open nbd // nbd_refs=3 NBD_CLEAR_SOCK // conf_refs=2 close nbd nbd_release nbd_config_put // conf_refs=1 nbd_put // nbd_refs=2 recv_work done // conf_refs=0, nbd_refs=1 rmmod // nbd_refs=0 Depends-on: e2daec488c57 ("nbd: Fix hungtask when nbd_config_put")
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-libbpf | Amazon Linux | 1:6.1.161-183.298.amzn2023 |
| perf6.12 | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| kernel-libbpf-devel | Amazon Linux | 1:6.1.161-183.298.amzn2023 |
| python3-perf | Amazon Linux | 1:6.1.161-183.298.amzn2023 |
| perf | Amazon Linux | 1:6.1.161-183.298.amzn2023 |
| kernel6.12-tools | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| kernel-livepatch-6.12.63-84.121 | Amazon Linux | 1:1.0-0.amzn2023 |
| kernel6.12-libbpf-devel | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-headers | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-tools-devel | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| linux_kernel | linux | 6.19, 6.18.2, 6.17.13, 6.12.63, 6.6.120, 6.1.160, 5.15.198, 5.10.248 |
| Linux | Linux | 9517b82d8d422d426a988b213fdd45c6b417b86d, 742012f6bf29553fdc460bf646a58df3a7b43d01, 5.10, 5.5, 443a1721806b6ff6303b5229e9811d68172d622f, 4.20, 4.15, 1ba2ced2bbdf7e64a30c3e88c70ea8bc208d1509 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 87aac3a80af5cbad93e63250e8a1e19095ba0d30, 87aac3a80af5cbad93e63250e8a1e19095ba0d30, 87aac3a80af5cbad93e63250e8a1e19095ba0d30 |
| Linux | Linux | 5.10, 0, 5.10.248 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel-livepatch-6.12.63-84.121 | 0 |
| linux | linux_kernel | 4.14.204, 5.10, 4.19.155 |
| amazon:2023 | kernel6.12-libbpf-devel | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| Linux | Linux | 5.9.5, 742fd49cf811ca164489e339b862e3fb8e240a73, 5.10 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel6.12-libbpf-static | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel-devel | 0 |
…and 12 more
Timeline
- Dec 23, 2025 CVE Published
- Dec 24, 2025 EPSS Score (30 in total, the first dated here)
- Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (141 in total, the first dated here)
- Mar 29, 2026 Security Advisory (147 in total, the first dated here)
- Sep 16, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-68372
vulnetix vdb fixes CVE-2025-68372
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-68372/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart