nday
CVE-2023-53233

net/smc: fix deadlock triggered by cancel_delayed_work_syn()

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 weakness typerace condition accesslocalno user interaction 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.

race condition
CWE-667, stated by the ADP CISA-ADP, NVD's analysts y NVD, republishing 134c704f-9b21-4f2e-91b3-4a467353bcc0
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from the ADP CISA-ADP
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from the ADP CISA-ADP
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
etapa
DIS
divulgación
cvss
5.5 MEDIUM v3.1

Ciclo de vida

Eje x en UTC; punto = minuto exacto, barra ancha = solo fecha, hueco = desconocida o inferida.
fecha desconocida
DISdivulgada
2025-09-15T14:22Z
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:

net/smc: fix deadlock triggered by cancel_delayed_work_syn()

The following LOCKDEP was detected:

Workqueue: events smc_lgr_free_work [smc]
WARNING: possible circular locking dependency detected
6.1.0-20221027.rc2.git8.56bc5b569087.300.fc36.s390x+debug #1 Not tainted
------------------------------------------------------
kworker/3:0/176251 is trying to acquire lock:
00000000f1467148 ((wq_completion)smc_tx_wq-00000000#2){+.+.}-{0:0},
	at: __flush_workqueue+0x7a/0x4f0
but task is already holding lock:
0000037fffe97dc8 ((work_completion)(&(&lgr->free_work)->work)){+.+.}-{0:0},
	at: process_one_work+0x232/0x730

which lock already depends on the new lock. the existing dependency chain (in reverse order) is:

	-> #4 ((work_completion)(&(&lgr->free_work)->work)){+.+.}-{0:0}:
	       __lock_acquire+0x58e/0xbd8
	       lock_acquire.part.0+0xe2/0x248
	       lock_acquire+0xac/0x1c8
	       __flush_work+0x76/0xf0
	       __cancel_work_timer+0x170/0x220
	       __smc_lgr_terminate.part.0+0x34/0x1c0 [smc]
	       smc_connect_rdma+0x15e/0x418 [smc]
	       __smc_connect+0x234/0x480 [smc]
	       smc_connect+0x1d6/0x230 [smc]
	       __sys_connect+0x90/0xc0
	       __do_sys_socketcall+0x186/0x370
	       __do_syscall+0x1da/0x208
	       system_call+0x82/0xb0
	-> #3 (smc_client_lgr_pending){+.+.}-{3:3}:
	       __lock_acquire+0x58e/0xbd8
	       lock_acquire.part.0+0xe2/0x248
	       lock_acquire+0xac/0x1c8
	       __mutex_lock+0x96/0x8e8
	       mutex_lock_nested+0x32/0x40
	       smc_connect_rdma+0xa4/0x418 [smc]
	       __smc_connect+0x234/0x480 [smc]
	       smc_connect+0x1d6/0x230 [smc]
	       __sys_connect+0x90/0xc0
	       __do_sys_socketcall+0x186/0x370
	       __do_syscall+0x1da/0x208
	       system_call+0x82/0xb0
	-> #2 (sk_lock-AF_SMC){+.+.}-{0:0}:
	       __lock_acquire+0x58e/0xbd8
	       lock_acquire.part.0+0xe2/0x248
	       lock_acquire+0xac/0x1c8
	       lock_sock_nested+0x46/0xa8
	       smc_tx_work+0x34/0x50 [smc]
	       process_one_work+0x30c/0x730
	       worker_thread+0x62/0x420
	       kthread+0x138/0x150
	       __ret_from_fork+0x3c/0x58
	       ret_from_fork+0xa/0x40
	-> #1 ((work_completion)(&(&smc->conn.tx_work)->work)){+.+.}-{0:0}:
	       __lock_acquire+0x58e/0xbd8
	       lock_acquire.part.0+0xe2/0x248
	       lock_acquire+0xac/0x1c8
	       process_one_work+0x2bc/0x730
	       worker_thread+0x62/0x420
	       kthread+0x138/0x150
	       __ret_from_fork+0x3c/0x58
	       ret_from_fork+0xa/0x40
	-> #0 ((wq_completion)smc_tx_wq-00000000#2){+.+.}-{0:0}:
	       check_prev_add+0xd8/0xe88
	       validate_chain+0x70c/0xb20
	       __lock_acquire+0x58e/0xbd8
	       lock_acquire.part.0+0xe2/0x248
	       lock_acquire+0xac/0x1c8
	       __flush_workqueue+0xaa/0x4f0
	       drain_workqueue+0xaa/0x158
	       destroy_workqueue+0x44/0x2d8
	       smc_lgr_free+0x9e/0xf8 [smc]
	       process_one_work+0x30c/0x730
	       worker_thread+0x62/0x420
	       kthread+0x138/0x150
	       __ret_from_fork+0x3c/0x58
	       ret_from_fork+0xa/0x40
	other info that might help us debug this:
	Chain exists of:
	  (wq_completion)smc_tx_wq-00000000#2
  	  --> smc_client_lgr_pending
	  --> (work_completion)(&(&lgr->free_work)->work)
	 Possible unsafe locking scenario:
	       CPU0                    CPU1
	       ----                    ----
	  lock((work_completion)(&(&lgr->free_work)->work));
	                   lock(smc_client_lgr_pending);
	                   lock((work_completion)
				(&(&lgr->free_work)->work));
	  lock((wq_completion)smc_tx_wq-00000000#2);
	 *** DEADLOCK ***
	2 locks held by kworker/3:0/176251:
	 #0: 0000000080183548
		((wq_completion)events){+.+.}-{0:0},
			at: process_one_work+0x232/0x730
	 #1: 0000037fffe97dc8
		((work_completion)
		 (&(&lgr->free_work)->work)){+.+.}-{0:0},
			at: process_one_work+0x232/0x730
	stack backtr

---truncated---

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

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS 3.1 vector from the CVE record, added by the ADP CISA-ADP.

Registro de eventos

+DISdivulgación

Linux publicó el registro CVE. CVSS 5.5, severidad media.

fuente cvelist · nday , importación masiva · en bruto
{
  "id": 309411,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2023-53233",
  "occurred_at": "2025-09-15T14:22:05.378Z",
  "observed_at": "2026-11-13T05:38:14.046808Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "adp:CISA-ADP",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "version": "3.1",
      "base_score": 5.5,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2026-01-14T17:55:41.706072Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2025-09-15T14:22:05.378Z",
    "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.