CVE-2025-40170: net: use dst_dev_rcu() in sk_setup_caps()
In the Linux kernel, the following vulnerability has been resolved:
net: use dstdevrcu() in sksetupcaps()
Use RCU to protect accesses to dst->dev from sksetupcaps() and skdstgsomaxsize().
Also use dstdevrcu() in ip6dstmtumaybeforward(), and ipdstmtumaybeforward().
ip4dsthoplimit() can use dstdevnetrcu().
Other sources
In the Linux kernel, the following vulnerability has been resolved:
net: use dstdevrcu() in sksetupcaps()
Use RCU to protect accesses to dst-dev from sksetupcaps() and skdstgsomaxsize().
Also use dstdevrcu() in ip6dstmtumaybeforward(), and ipdstmtumaybeforward().
ip4dsthoplimit() can use dstdevnetrcu().
— IBM
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.69-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.17.6-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.17.3 - Upgrade
Upgrade
azurelinux/kernelto a version that resolves this vulnerability.Fixed in 6.6.161.1-1 - Upgrade
Upgrade
ubuntu/linux-aws-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1007.7~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1008.8~24.04.1 - Upgrade
Upgrade
ubuntu/linux-nvidia-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1008.8 - Upgrade
Upgrade
ubuntu/linux-nvidia-tegrato a version that resolves this vulnerability.Fixed in 6.8.0-1035.38 - Upgrade
Upgrade
ubuntu/linux-oem-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1011.11 - Upgrade
Upgrade
ubuntu/linux-oracle-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1007.7~24.04.1 - Upgrade
Upgrade
ubuntu/linux-realtime-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1006.7~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 6.17.0-14.14 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 6.17.0-1007.7 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 6.17.0-1008.8 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 6.17.0-1007.7 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 6.17.0-1007.7 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 6.17.0-1008.8 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 6.17.0-1006.7 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 6.17.0-14.14.1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.15-1Fixed in 7.3.3-1 - Compensating control
Update the Linux kernel networking code to use dst_dev_rcu() for accesses to dst->dev in sk_setup_caps(), sk_dst_gso_max_size(), ip6_dst_mtu_maybe_forward(), and ip_dst_mtu_maybe_forward(); use dst_dev_net_rcu() in ip4_dst_hoplimit().
Event History
Frequently Asked Questions
What is the severity of CVE-2025-40170?
CVE-2025-40170 has a high severity level due to its potential impact on system stability and security.
How do I fix CVE-2025-40170?
To fix CVE-2025-40170, update the Linux kernel to the latest version that contains the patch for this vulnerability.
What systems are affected by CVE-2025-40170?
CVE-2025-40170 affects the Linux kernel across various distributions that utilize the impacted versions.
What are the risks associated with CVE-2025-40170?
The risks associated with CVE-2025-40170 include possible system crashes and exploitation leading to potential unauthorized access.
Is there a workaround for CVE-2025-40170?
There are no recommended workarounds for CVE-2025-40170; applying the kernel update is the best course of action.