CVE-2025-40357
General Protection Fault in Linux Kernel net/smc Component
Publication date: 2025-12-16
Last updated on: 2025-12-16
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a general protection fault (crash) in the Linux kernel related to the net/smc module, specifically in the __smc_diag_dump function. Detection involves monitoring kernel logs for Oops messages indicating a general protection fault with references to smc_diag.c and smc_diag_dump. You can check the kernel ring buffer for such messages using the command: dmesg | grep -i 'smc_diag' or dmesg | grep -i 'general protection fault'. Additionally, monitoring for crashes or oops events related to smc_diag_dump in /var/log/kern.log or /var/log/messages can help detect this issue. There are no specific network commands provided to detect this vulnerability directly, but kernel log inspection is key.
Can you explain this vulnerability to me?
This vulnerability is a general protection fault in the Linux kernel's net/smc subsystem, specifically in the __smc_diag_dump function. It occurs due to an unexpected change of the smc->clcsock pointer in the inet_init_csk_locks() function, which leads to a crash when the system tries to access an invalid or non-canonical memory address. The issue arises because the INET_PROTOSW_ICSK flag was incorrectly used by smc, causing improper handling of socket structures and resulting in a kernel crash.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a general protection fault, leading to system instability or denial of service. Since it involves kernel memory access errors, it may disrupt normal network operations on affected systems, potentially causing downtime or requiring a reboot to recover.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by removing the INET_PROTOSW_ICSK flag from the smc implementation and reverting a previous commit that caused unsafe casting. Immediate mitigation would involve updating the Linux kernel to a version that includes this fix to prevent the general protection fault in __smc_diag_dump.