Description
In the Linux kernel, the following vulnerability has been resolved: net: fix possible store tearing in neigh_periodic_work() While looking at a related syzbot report involving neigh_periodic_work(), I found that I forgot to add an annotation when deleting an RCU protected item from a list. Readers use rcu_deference(*np), we need to use either rcu_assign_pointer() or WRITE_ONCE() on writer side to prevent store tearing. I use rcu_assign_pointer() to have lockdep support, this was the choice made in neigh_flush_dev().
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
767e97e1e0db0d0f3152cd2f3bd3403596aedbad to < 95eabb075a5902f4c0834ab1fb12dc35730c05afaffected767e97e1e0db0d0f3152cd2f3bd3403596aedbad to < 2ea52a2fb8e87067e26bbab4efb8872639240eb0affected767e97e1e0db0d0f3152cd2f3bd3403596aedbad to < 147d89ee41434b97043c2dcb17a97dc151859baaaffected767e97e1e0db0d0f3152cd2f3bd3403596aedbad to < f82aac8162871e87027692b36af335a2375d4580affected767e97e1e0db0d0f3152cd2f3bd3403596aedbad to < a75152d233370362eebedb2643592e7c883cc9fcaffected767e97e1e0db0d0f3152cd2f3bd3403596aedbad to < 25563b581ba3a1f263a00e8c9a97f5e7363be6fdaffected
Linux Linux
Default version status: affected
2.6.37affected0 to < 2.6.37unaffected5.4.258 to ≤ 5.4.*unaffected5.10.198 to ≤ 5.10.*unaffected5.15.135 to ≤ 5.15.*unaffected6.1.57 to ≤ 6.1.*unaffected6.5.7 to ≤ 6.5.*unaffected6.6 to ≤ *unaffected
References
- https://git.kernel.org/stable/c/95eabb075a5902f4c0834ab1fb12dc35730c05af ↗
- https://git.kernel.org/stable/c/2ea52a2fb8e87067e26bbab4efb8872639240eb0 ↗
- https://git.kernel.org/stable/c/147d89ee41434b97043c2dcb17a97dc151859baa ↗
- https://git.kernel.org/stable/c/f82aac8162871e87027692b36af335a2375d4580 ↗
- https://git.kernel.org/stable/c/a75152d233370362eebedb2643592e7c883cc9fc ↗
- https://git.kernel.org/stable/c/25563b581ba3a1f263a00e8c9a97f5e7363be6fd ↗