CVE-2026-68286

drop_monitor: perform u64_stats updates under IRQ-disabled section

N/A
Published: August 10, 2026 at 12:02 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.4 ≤ v < 6.1.1895.4 ≤ v < 6.12.1115.4 ≤ v < 6.18.535.4 ≤ v < 6.6.1585.4 ≤ v < 7.1.65.4 ≤ v < 7.25.4e9feb58020f952f7d9de785ede9a7d54ab1eda5c
Vendor states this is fixed in 3454c729ee8aa682ec871f1b174b047f731933ae (fixed)
Vendor states this is fixed in 7d857cf5f0120bb0e020fa20b03bd21b9d3e0c04 (fixed)
Vendor states this is fixed in be9b121894d6ad44f0011f79543a2e3245979497 (fixed)
Vendor states this is fixed in d5e2cd2bc8ae36617346b3a54ee9da61d866bf92 (fixed)
Vendor states this is fixed in dd8472526a04f2185afd792b8041a912a7d75d85 (fixed)
Vendor states this is fixed in fd098a23bf8fda7eae48db9b06e7c34fc4d228fa (fixed)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card