Answer in brief
CVE-2023-54318 records a High severity (CVSS 8.8) vulnerability in net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1f90a05d9ff907c70456e7c9d7058372679a88c6 <d1c6c93c27a4bf48006ab16cd9b38d85559d7645 || >=1f90a05d9ff907c70456e7c9d7058372679a88c6 <06b4934ab2b534bb92935c7601852066ebb9eab8 || >=1f90a05d9ff907c70456e7c9d7058372679a88c6 <70c8d17007dc4a07156b7da44509527990e569b3 || >=1f90a05d9ff907c70456e7c9d7058372679a88c6 <b717463610a27fc0b58484cfead7a623d5913e61 || >=1f90a05d9ff907c70456e7c9d7058372679a88c6 <f5146e3ef0a9eea405874b36178c19a4863b8989 | d1c6c93c27a4bf48006ab16cd9b38d85559d7645, 06b4934ab2b534bb92935c7601852066ebb9eab8, 70c8d17007dc4a07156b7da44509527990e569b3, b717463610a27fc0b58484cfead7a623d5913e61, f5146e3ef0a9eea405874b36178c19a4863b8989 |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Dec 30, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add While doing smcr_port_add, there maybe linkgroup add into or delete from smc_lgr_list.list at the same time, which may result kernel crash. So, use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add. The crash calltrace show below: BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 0 PID: 559726 Comm: kworker/0:92 Kdump: loaded Tainted: G Hardware name: Alibaba Cloud Alibaba Cloud ECS, BIOS 449e491 04/01/2014 Workqueue: events smc_ib_port_event_work [smc] RIP: 0010:smcr_port_add+0xa6/0xf0 [smc] RSP: 0000:ffffa5a2c8f67de0 EFLAGS: 00010297 RAX: 0000000000000001 RBX: ffff9935e0650000 RCX: 0000000000000000 RDX: 0000000000000010 RSI: ffff9935e0654290 RDI: ffff9935c8560000 RBP: 0000000000000000 R08: 0000000000000000 R09: ffff9934c0401918 R10: 0000000000000000 R11: ffffffffb4a5c278 R12: ffff99364029aae4 R13: ffff99364029aa00 R14: 00000000ffffffed R15: ffff99364029ab08 FS: 0000000000000000(0000) GS:ffff994380600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000f06a10003 CR4: 0000000002770ef0 PKRU: 55555554 Call Trace: smc_ib_port_event_work+0x18f/0x380 [smc] process_one_work+0x19b/0x340 worker_thread+0x30/0x370 ? process_one_work+0x340/0x340 kthread+0x114/0x130 ? __kthread_cancel_work+0x50/0x50 ret_from_fork+0x1f/0x30
Quoted source text, attributed separately from HOL analysis.