CVE-2026-68286
drop_monitor: perform u64_stats updates under IRQ-disabled section
Reported by linux · Published August 10, 2026
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.
EPSS 0.21% · 11.4th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | fd098a23bf8fda7eae48db9b06e7c34fc4d228fa, dd8472526a04f2185afd792b8041a912a7d75d85, d5e2cd2bc8ae36617346b3a54ee9da61d866bf92, be9b121894d6ad44f0011f79543a2e3245979497, 7d857cf5f0120bb0e020fa20b03bd21b9d3e0c04, 3454c729ee8aa682ec871f1b174b047f731933ae |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | e9feb58020f952f7d9de785ede9a7d54ab1eda5c, e9feb58020f952f7d9de785ede9a7d54ab1eda5c, e9feb58020f952f7d9de785ede9a7d54ab1eda5c |
| Linux | Linux | 5.4, 0, 6.1.189 |
| Linux | Linux | 6.6.158, 0, 7.1.6 |
| linux | linux_kernel | 5.4, 5.4, 5.4 |
Timeline
- Aug 10, 2026 CVE Published
- Aug 11, 2026 Coalition ESS Score
- Aug 16, 2026 Security Advisory
- Aug 24, 2026 EPSS Score (16 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-68286
vulnetix vdb fixes CVE-2026-68286
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-68286/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart