Threats Tagged 'cve-2025-40139'
View all threats tagged with 'cve-2025-40139'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2025-40139'
Click on any threat for detailed analysis and mitigation recommendations
A use-after-free (UAF) vulnerability in the Linux kernel's smc_clc_prfx_set() function was resolved by changing how socket destination device references are accessed. The flaw involved unsafe use of sk_dst_get(sk)->dev without proper synchronization, which could lead to memory corruption. The fix uses __sk_dst_get() and dst_dev_rcu() under RCU read lock to prevent UAF. This vulnerability affects local attackers with low privileges and can result in high impact on confidentiality, integrity, and availability. Join the discussion | GCVE Database | 11/12/2025, 12:30:27 UTC Added: 07/30/2026, 15:50:46 UTC |
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. Join the discussion | GCVE Database | 11/12/2025, 11:15:00 UTC Added: 07/18/2026, 11:37:38 UTC |
Showing 1 to 2 of 2 results