CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's handling of the VALID marking in the net shaper component, where a race condition can lead to a use-after-free (UAF) scenario. This flaw allows a reader to observe a VALID mark on an entry that may be replaced by a writer, potentially leading to memory corruption and system instability. Organizations using Linux-based systems, particularly those relying on the networking stack, should prioritize patching this vulnerability to mitigate the risk of exploitation.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: net: shaper: rework the VALID marking (again) Recent commit changed the semantics from NOT_VALID to VALID. I didn't realize that the flags are not stored atomically with the entry in XArray. There's still a race of reader observing a VALID mark for a slot, getting interrupted, writer replacing the entry with a different one, reader continuing, fetching the entry which is now a different pointer than the pointer for which VALID was meant. The biggest consequence of this is that we may see a UAF since net_shaper_rollback() assumed that entries without VALID can be freed without observing RCU. Looks like the XArray marks are buying us nothing at this point. Let's convert the code to an explicit valid field. The smp_load_acquire() / smp_store_release() barriers are marginally cleaner.