Answer in brief
CVE-2025-40139 records a Unknown severity vulnerability in smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set().. 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.
A CVSS score is not reported in the current record. 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 | >=a046d57da19f812216f393e7c535f5858f793ac3 <0736993bfe5c7a9c744ae3fac62d769dfdae54e1 || >=a046d57da19f812216f393e7c535f5858f793ac3 <935d783e5de9b64587f3adb25641dd8385e64ddb | 0736993bfe5c7a9c744ae3fac62d769dfdae54e1, 935d783e5de9b64587f3adb25641dd8385e64ddb |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Nov 12, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 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: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set(). smc_clc_prfx_set() is called during connect() and not under RCU nor RTNL. Using sk_dst_get(sk)->dev could trigger UAF. Let's use __sk_dst_get() and dev_dst_rcu() under rcu_read_lock() after kernel_getsockname(). Note that the returned value of smc_clc_prfx_set() is not used in the caller. While at it, we change the 1st arg of smc_clc_prfx_set[46]_rcu() not to touch dst there.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-40139 records a Unknown severity vulnerability in smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set().. 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.
A CVSS score is not reported in the current record. 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 | >=a046d57da19f812216f393e7c535f5858f793ac3 <0736993bfe5c7a9c744ae3fac62d769dfdae54e1 || >=a046d57da19f812216f393e7c535f5858f793ac3 <935d783e5de9b64587f3adb25641dd8385e64ddb | 0736993bfe5c7a9c744ae3fac62d769dfdae54e1, 935d783e5de9b64587f3adb25641dd8385e64ddb |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Nov 12, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 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: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set(). smc_clc_prfx_set() is called during connect() and not under RCU nor RTNL. Using sk_dst_get(sk)->dev could trigger UAF. Let's use __sk_dst_get() and dev_dst_rcu() under rcu_read_lock() after kernel_getsockname(). Note that the returned value of smc_clc_prfx_set() is not used in the caller. While at it, we change the 1st arg of smc_clc_prfx_set[46]_rcu() not to touch dst there.
Quoted source text, attributed separately from HOL analysis.