Answer in brief
CVE-2022-48751 records a High severity (CVSS 7.8) vulnerability in net/smc: Transitional solution for clcsock race issue. 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 7.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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.17:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fd57770dd198f5b2ddd5b9e6bf282cf98d63adb9 <38f0bdd548fd2ef5d481b88d8a2bfef968452e34 || >=fd57770dd198f5b2ddd5b9e6bf282cf98d63adb9 <4284225cd8001e134f5cf533a7cd244bbb654d0f || >=fd57770dd198f5b2ddd5b9e6bf282cf98d63adb9 <c0bf3d8a943b6f2e912b7c1de03e2ef28e76f760 || d1d004585b40c212b338fc8a40cbaaf230ea4703 || >=4.19.299 <4.20 | 38f0bdd548fd2ef5d481b88d8a2bfef968452e34, 4284225cd8001e134f5cf533a7cd244bbb654d0f, c0bf3d8a943b6f2e912b7c1de03e2ef28e76f760, 4.20 |
| Linux/Linuxgeneric | 5.1 | Not reported |
Published upstream
Jun 20, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: net/smc: Transitional solution for clcsock race issue We encountered a crash in smc_setsockopt() and it is caused by accessing smc->clcsock after clcsock was released. BUG: kernel NULL pointer dereference, address: 0000000000000020 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 50309 Comm: nginx Kdump: loaded Tainted: G E 5.16.0-rc4+ #53 RIP: 0010:smc_setsockopt+0x59/0x280 [smc] Call Trace: <TASK> __sys_setsockopt+0xfc/0x190 __x64_sys_setsockopt+0x20/0x30 do_syscall_64+0x34/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f16ba83918e </TASK> This patch tries to fix it by holding clcsock_release_lock and checking whether clcsock has already been released before access. In case that a crash of the same reason happens in smc_getsockopt() or smc_switch_to_fallback(), this patch also checkes smc->clcsock in them too. And the caller of smc_switch_to_fallback() will identify whether fallback succeeds according to the return value.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-48751 records a High severity (CVSS 7.8) vulnerability in net/smc: Transitional solution for clcsock race issue. 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 7.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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.17:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fd57770dd198f5b2ddd5b9e6bf282cf98d63adb9 <38f0bdd548fd2ef5d481b88d8a2bfef968452e34 || >=fd57770dd198f5b2ddd5b9e6bf282cf98d63adb9 <4284225cd8001e134f5cf533a7cd244bbb654d0f || >=fd57770dd198f5b2ddd5b9e6bf282cf98d63adb9 <c0bf3d8a943b6f2e912b7c1de03e2ef28e76f760 || d1d004585b40c212b338fc8a40cbaaf230ea4703 || >=4.19.299 <4.20 | 38f0bdd548fd2ef5d481b88d8a2bfef968452e34, 4284225cd8001e134f5cf533a7cd244bbb654d0f, c0bf3d8a943b6f2e912b7c1de03e2ef28e76f760, 4.20 |
| Linux/Linuxgeneric | 5.1 | Not reported |
Published upstream
Jun 20, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: net/smc: Transitional solution for clcsock race issue We encountered a crash in smc_setsockopt() and it is caused by accessing smc->clcsock after clcsock was released. BUG: kernel NULL pointer dereference, address: 0000000000000020 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 50309 Comm: nginx Kdump: loaded Tainted: G E 5.16.0-rc4+ #53 RIP: 0010:smc_setsockopt+0x59/0x280 [smc] Call Trace: <TASK> __sys_setsockopt+0xfc/0x190 __x64_sys_setsockopt+0x20/0x30 do_syscall_64+0x34/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f16ba83918e </TASK> This patch tries to fix it by holding clcsock_release_lock and checking whether clcsock has already been released before access. In case that a crash of the same reason happens in smc_getsockopt() or smc_switch_to_fallback(), this patch also checkes smc->clcsock in them too. And the caller of smc_switch_to_fallback() will identify whether fallback succeeds according to the return value.
Quoted source text, attributed separately from HOL analysis.