CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's drop_monitor functionality, where improper handling of 64-bit statistics updates can lead to corruption of seqcount state or stats values due to reentrant updates during nested interrupts. This issue primarily impacts systems running on 32-bit architectures, where the execution context of tracepoint probes may allow for concurrent updates. Organizations utilizing Linux kernel versions with this vulnerability should prioritize patching to mitigate potential instability and data integrity issues in their network monitoring systems.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: drop_monitor: perform u64_stats updates under IRQ-disabled section In net_dm_packet_trace_kfree_skb_hit() and net_dm_hw_trap_packet_probe(), u64_stats_update_begin() / u64_stats_inc() / u64_stats_update_end() were called after spin_unlock_irqrestore(&...drop_queue.lock, flags), when local IRQs had already been re-enabled. Tracepoint probes can execute in IRQ or softirq context. On 32-bit architectures, u64_stats_update_begin() disables preemption but not interrupts, relying on seqcount writes. If a nested interrupt occurs on the same CPU during the 64-bit stats update, the reentrant seqcount update can corrupt the seqcount state or stats value. Fix this by performing the 64-bit per-CPU stats update before releasing drop_queue.lock via spin_unlock_irqrestore(), ensuring local interrupts remain disabled during the u64_stats update.