Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68372: nbd: defer config put in recv_work

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 198aa230a6f8c1f6af7ed26b29180749c3e79e4d, 1ba2ced2bbdf7e64a30c3e88c70ea8bc208d1509, 3692884bd6187d89d41eef81e5a9724519fd01c1.

Low priority for now. Upgrade to Linux Linux 198aa230a6f8c1f6af7ed26b29180749c3e79e4d, 1ba2ced2bbdf7e64a30c3e88c70ea8bc208d1509, 3692884bd6187d89d41eef81e5a9724519fd01c1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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")

—No exploit Fix available
Published
Dec 24, 2025
Updated
Oct 13, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68372

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 0a4e383fc3aa6540f804c4fd1184a96ae5de6ef8, 2ef6f4bd60411934e3fc2715442c2afe70f84bf3, 742fd49cf811ca164489e339b862e3fb8e240a73, 14df8724aeeef338172e2a2d6efadc989921ca0f, 5.10affected
    • 87aac3a80af5cbad93e63250e8a1e19095ba0d30 and later · before 198aa230a6f8c1f6af7ed26b29180749c3e79e4daffected · git
    • 87aac3a80af5cbad93e63250e8a1e19095ba0d30 and later · before d3ba312675911ff9e3fefefd551751e153a9f0a9affected · git
    • 87aac3a80af5cbad93e63250e8a1e19095ba0d30 and later · before 3692884bd6187d89d41eef81e5a9724519fd01c1affected · git
    • 87aac3a80af5cbad93e63250e8a1e19095ba0d30 and later · before 1ba2ced2bbdf7e64a30c3e88c70ea8bc208d1509affected · git
    • 87aac3a80af5cbad93e63250e8a1e19095ba0d30 and later · before 6b69593f72e1bfba6ca47ca8d9b619341fded7d6affected · git
    • 87aac3a80af5cbad93e63250e8a1e19095ba0d30 and later · before 443a1721806b6ff6303b5229e9811d68172d622faffected · git
    • 87aac3a80af5cbad93e63250e8a1e19095ba0d30 and later · before 742012f6bf29553fdc460bf646a58df3a7b43d01affected · git
    • 87aac3a80af5cbad93e63250e8a1e19095ba0d30 and later · before 9517b82d8d422d426a988b213fdd45c6b417b86daffected · git
    • 4.14.204 and later · before 4.15affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.13-16.17.13-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68370Dec 24, 2025 · coresight: tmc: add the handle of the event to the path
    31Monitor
  • ← EarlierCVE-2025-68371Dec 24, 2025 · scsi: smartpqi: Fix device resources accessed after device removal
    0Monitor
  • Later →CVE-2025-68373Dec 24, 2025 · md: avoid repeated calls to del_gendisk
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux198aa230a6f8c1f6af7ed26b29180749c3e79e4dVendor (CNA)
Linux Linux1ba2ced2bbdf7e64a30c3e88c70ea8bc208d1509Vendor (CNA)
Linux Linux3692884bd6187d89d41eef81e5a9724519fd01c1Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux443a1721806b6ff6303b5229e9811d68172d622fVendor (CNA)
Linux Linux5.10Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux6b69593f72e1bfba6ca47ca8d9b619341fded7d6Vendor (CNA)
Linux Linux742012f6bf29553fdc460bf646a58df3a7b43d01Vendor (CNA)
Linux Linux9517b82d8d422d426a988b213fdd45c6b417b86dVendor (CNA)
Linux Linuxd3ba312675911ff9e3fefefd551751e153a9f0a9Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records