drop_monitor: perform u64_stats updates under IRQ-disabled section
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e9feb58020f952f7d9de785ede9a7d54ab1eda5c · < fd098a23bf8fda7eae48db9b06e7c34fc4d228fa| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s drop_monitor updates 64-bit statistics after re-enabling local interrupts. On 32-bit systems, an interrupt during an update can corrupt the sequence counter or statistics value. The input does not specify an attacker path, authentication requirement, or user interaction.
Operators running the Linux kernel on 32-bit systems should check whether their kernel includes the drop_monitor fix; affected versions are not specified.