xfrm: state: initialize state_ptrs earlier in xfrm_state_find
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 94d077c331730510d5611b438640a292097341f0, Kernel 6.12.41, Kernel 6.14 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: xfrm: state: initialize state_ptrs earlier in xfrm_state_find In case of preemption, xfrm_state_look_at will find a different pcpu_id and look up states for that other CPU. If we matched a state for CPU2 in the state_cache while the lookup started on CPU1, we will jump to "found", but the "best" state that we got will be ignored and we will enter the "acquire" block. This block uses state_ptrs, which isn't initialized at this point. Let's initialize state_ptrs just after taking rcu_read_lock. This will also prevent a possible misuse in the future, if someone adjusts this function.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=e952837f3ddb0ff726d5b582aa1aad9aa38d024d <94d077c331730510d5611b438640a292097341f0, >=6.12.13 <6.12.41, >=6.13.2 <6.14, >=6.6.120 <6.7, >=a16871c7832ea6435abb6e0b58289ae7dcb7e4fc <6bf2daafc51bcb9272c0fdff2afd38217337d0d3, >=e952837f3ddb0ff726d5b582aa1aad9aa38d024d <463562f9591742be62ddde3b426a0533ed496955, =6.14, =80610185e9dd2ef7c0a4818a47390a8655b3dc27, =b86dc510308d7a8955f3f47a4fea4bef887653e4, =dd4c2a174994238d55ab54da2545543d36f4e0d0, >=6.1.191 <6.2 | 94d077c331730510d5611b438640a292097341f0, 6.12.41, 6.14, 6.7, 6bf2daafc51bcb9272c0fdff2afd38217337d0d3, 463562f9591742be62ddde3b426a0533ed496955, 6.2 |
| linux-kernel: Kernel | >=6.12.13 <6.12.41, >=6.13.2 <6.14, >=6.14.0 <6.15.9, >=6.6.120 <6.7, >=6.1.191 <6.2 | 6.12.41, 6.14, 6.15.9, 6.7, 6.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket