In the Linux kernel, the following vulnerability has been resolved:ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_init_flow()There are code paths from which the function is called without holdingthe RCU read lock, resulting in a suspicious RCU usage warning [1].Fix by using l3mdev_master_upper_ifindex_by_index() which will acquirethe RCU read lock before callingl3mdev_master_upper_ifindex_by_index_rcu().[1]WARNING: suspicious RCU usage6.12.0-rc3-custom-gac8f72681cf2 #141 Not tainted-----------------------------net/core/dev.c:876 RCU-list traversed in non-reader section!!other info that might help us debug this:rcu_scheduler_active = 2, debug_locks = 11 lock held by ip/361: #0: ffffffff86fc7cb0 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x377/0xf60stack backtrace:CPU: 3 UID: 0 PID: 361 Comm: ip Not tainted 6.12.0-rc3-custom-gac8f72681cf2 #141Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011Call Trace:
No PoCs from references.
- https://github.com/w4zu/Debian_security