nday
CVE-2025-68372

nbd: defer config put in recv_work

Linux / Linux

Fecha de divulgación: . nday aún no tiene constancia de una corrección; eso no significa que no exista parche. Ninguna de las cuatro fuentes de PoC la recoge. No figura en el KEV de CISA.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
etapa
DIS
divulgación
cvss
sin puntuación aún

Ciclo de vida

Eje x en UTC; punto = minuto exacto, barra ancha = solo fecha, hueco = desconocida o inferida.
fecha desconocida
DISdivulgada
2025-12-24T10:33Z
PATparcheada
sin registro aún
ANAanalizada
sin registro aún
POCPoC
sin registro aún
ITWexplotada
sin registro aún
KEVen KEV
sin registro aún

Descripción

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

Original text of the CVE record (cvelist), shown as published.

Registro de eventos

+DISdivulgación

Linux publicó el registro CVE.

fuente cvelist · nday , importación masiva · en bruto
{
  "id": 391134,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2025-68372",
  "occurred_at": "2025-12-24T10:33:02.679Z",
  "observed_at": "2026-11-13T05:39:20.395751Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "ssvc": {
      "timestamp": "2026-06-16T19:28:28.671225Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2025-12-24T10:33:02.679Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Debate de investigadores

0 investigadores lo mencionaron en los últimos 7 días

Publicaciones en X de investigadores de la lista de nday que mencionan este CVE, tal como se publicaron. nday no las verifica.

nday aún no ha recopilado publicaciones en X de investigadores de su lista sobre este CVE.

Discussion

0 comments

No comments yet.