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.
Published: 2026-08-10
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability occurs when the Linux kernel performs 64‑bit per‑CPU statistics updates after local interrupts have been re‑enabled. On 32‑bit processors the update routine disables only preemption, not interrupts. When a nested interrupt occurs on the same CPU during the update, the reentrant sequence count can be corrupted, altering statistical counters that the kernel uses for diagnostics or accounting. The compromised data can lead to incorrect resource accounting or misleading telemetry, potentially affecting system monitoring or decision‑making that relies on these counters.

Affected Systems

All Linux kernel configurations that include the net_dm packet trace, drop monitor, or hardware trap packet probe hooks are affected when the code paths remain enabled. The specific kernel version numbers are not listed in the data therefore any kernel release that has not applied the upstream fix for this drop monitoring issue is potentially vulnerable. The vulnerability is relevant to 32‑bit architectures where the kernel uses u64_stats_update_begin() for per‑CPU statistics tracking.

Risk and Exploitability

The CVSS score of 5.3 indicates a medium severity, while the EPSS score of < 1% reflects a very low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog, meaning no known public exploits are reported. It is inferred that an attacker would likely need local access with sufficient privileges to activate the packet tracing hooks or otherwise trigger the vulnerable code paths, so the attack vector is effectively local. Given the low exploitation probability and lack of documented attacks, the overall risk is low to moderate.

Generated by OpenCVE AI on August 13, 2026 at 06:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a kernel update that contains the upstream fix for the drop monitoring statistics update issue.
  • If an upgrade is not yet possible, disable the net_dm packet tracing, drop monitor, or hardware trap packet probe features through sysctl settings or module configuration to prevent execution of the vulnerable paths.
  • If the kernel is running a module that includes these hooks, unload or rebuild the module without the tracing functionality as a temporary mitigation.

Generated by OpenCVE AI on August 13, 2026 at 06:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 13 Aug 2026 04:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-754

Wed, 12 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-364
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H'}

threat_severity

Moderate


Mon, 10 Aug 2026 18:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-754

Mon, 10 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
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.
Title drop_monitor: perform u64_stats updates under IRQ-disabled section
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:02:21.413Z

Reserved: 2026-07-30T09:28:09.379Z

Link: CVE-2026-68286

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-10T13:20:17.903

Modified: 2026-08-17T05:18:31.277

Link: CVE-2026-68286

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-10T12:02:19Z

Links: CVE-2026-68286 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T06:30:05Z

Weaknesses
  • CWE-364

    Signal Handler Race Condition