smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set().
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.187, 6.6.156, 6.12.108, 6.17.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From a046d57da19f812216f393e7c535f5858f793ac3 · fixed in 5a2fccc4b32c13ddde3676f9e15e1a9baa7d6fde; From a046d57da19f812216f393e7c535f5858f793ac3 · fixed in 80d1fd39f4e37d836655e9f7ffccaf78925049bf; From a046d57da19f812216f393e7c535f5858f793ac3 · fixed in 956c57daba55cf9ed25d9f2512883b8a1a927599; From a046d57da19f812216f393e7c535f5858f793ac3 · fixed in 0736993bfe5c7a9c744ae3fac62d769dfdae54e1; From a046d57da19f812216f393e7c535f5858f793ac3 · fixed in 935d783e5de9b64587f3adb25641dd8385e64ddb
- Linux Linux
4.11
- KernelLinux
From 4.11.0 · fixed in 6.1.187; From 6.2.0 · fixed in 6.6.156; From 6.7.0 · fixed in 6.12.108; From 6.13.0 · fixed in 6.17.3