First published: Fri Sep 06 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets.
Affected Software | Affected Version | How to fix |
---|---|---|
F5 Traffix Systems Signaling Delivery Controller | =5.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
F5-K000140987 is classified as a medium severity vulnerability.
To fix F5-K000140987, upgrade to the patched version of F5 Traffix SDC 5.2.0 or later.
F5-K000140987 is a race condition vulnerability in the Linux kernel related to improper RCU rules.
F5-K000140987 affects the F5 Traffix Systems Signaling Delivery Controller version 5.2.0.
Exploitation of F5-K000140987 could lead to a use-after-free condition, potentially resulting in system instability.