---
id: CVE-2024-56641
title: 'kernel: net/smc: initialize close_work early to avoid warning (CVE-2024-56641)'
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  net/smc: initialize close_work early to avoid warning

  We encountered a warning that close_work was canceled before
  initialization.

    WARNING: CPU: 7 PID: 111103 at kern…
severity: low
cvss: 3.3
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'
cvssSource: vendor
cwe: CWE-665
vendor: Red Hat
product: Red Hat Enterprise Linux 9
affected:
  - enterprise_linux 8
  - enterprise_linux 9
published: '2024-12-27'
updated: '2026-10-16'
sourceUpdated: '2026-10-16T23:07:50+00:00'
source: CSAF
sourceUrl: 'https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-56641.json'
references:
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-56641.json
  - url: 'https://access.redhat.com/security/cve/CVE-2024-56641'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2334558'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2024-56641'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2024-56641'
  - url: >-
      https://lore.kernel.org/linux-cve-announce/2024122736-CVE-2024-56641-5492@gregkh/T
  - url: 'https://git.kernel.org/stable/c/f0c37002210aaede10dae849d1a78efc2243add2'
  - url: 'https://git.kernel.org/stable/c/6638e52dcfafaf1b9cbc34544f0c832db0069ea1'
  - url: 'https://git.kernel.org/stable/c/0541db8ee32c09463a72d0987382b3a3336b0043'
tags:
  - csaf
  - vex
  - red-hat
  - cve.org
  - score-dispute
epss: 0.00515
epssPercentile: 0.4306
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-10-15T21:41:11.352533Z'
scores:
  vendor: 3.3
  cna: 7.5
ingestedAt: '2026-10-15T22:48:25.445Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

net/smc: initialize close_work early to avoid warning

We encountered a warning that close_work was canceled before
initialization.

  WARNING: CPU: 7 PID: 111103 at kernel/workqueue.c:3047 __flush_work+0x19e/0x1b0
  Workqueue: events smc_lgr_terminate_work [smc]
  RIP: 0010:__flush_work+0x19e/0x1b0
  Call Trace:
   ? __wake_up_common+0x7a/0x190
   ? work_busy+0x80/0x80
   __cancel_work_timer+0xe3/0x160
   smc_close_cancel_work+0x1a/0x70 [smc]
   smc_close_active_abort+0x207/0x360 [smc]
   __smc_lgr_terminate.part.38+0xc8/0x180 [smc]
   process_one_work+0x19e/0x340
   worker_thread+0x30/0x370
   ? process_one_work+0x340/0x340
   kthread+0x117/0x130
   ? __kthread_cancel_work+0x50/0x50
   ret_from_fork+0x22/0x30

This is because when smc_close_cancel_work is triggered, e.g. the RDMA
driver is rmmod and the LGR is terminated, the conn->close_work is
flushed before initialization, resulting in WARN_ON(!work->func).

__smc_lgr_terminate             | smc_connect_{rdma|ism}
-------------------------------------------------------------
                                | smc_conn_create
				| \- smc_lgr_register_conn
for conn in lgr->conns_all      |
\- smc_conn_kill                |
   \- smc_close_active_abort    |
      \- smc_close_cancel_work  |
         \- cancel_work_sync    |
            \- __flush_work     |
	         (close_work)   |
	                        | smc_close_init
	                        | \- INIT_WORK(&close_work)

So fix this by initializing close_work before establishing the
connection.

## Vendor advisories

- **Red Hat VEX** · Low · affected: Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9 · no fix planned: Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9 · updated 2026-10-16 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-56641.json)

**kernel: net/smc: initialize close_work early to avoid warning** — rated Low by Red Hat. Released 2024-12-27, updated 2026-10-16.

Affected:

- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 9

No fix planned:

- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 9

Not affected:

- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 7

## Remediation

Out of support scope

Workarounds / mitigations:

- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.