CVE-2024-56641: Linux kernel · net/smc: initialize close_work early to avoid warning
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.8.0-1027.29~22.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-1027.29~22.04.1, 6.8.0-1027.32~22.04.1, 6.8.0-1028.30~22.04.1 +30
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux@6.8.0-58.60?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws@6.8.0-1027.29?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure@6.8.0-1027.32?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11@6.11.0-1012.12~24.04.1?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia@6.8.0-1014.15?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp@6.8.0-1028.30?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-56641 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-56641 (opens in a new tab)
- git.kernel.org/linus/0541db8ee32c09463a72d0987382b3a3336b0043 (opens in a new tab)
- git.kernel.org/stable/c/0541db8ee32c09463a72d0987382b3a3336b0043 (opens in a new tab)
- git.kernel.org/stable/c/6638e52dcfafaf1b9cbc34544f0c832db0069ea1 (opens in a new tab)
- git.kernel.org/stable/c/f0c37002210aaede10dae849d1a78efc2243add2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7380-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7381-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7382-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7450-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7451-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7452-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7453-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7468-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7523-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7524-1 (opens in a new tab)