Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68286drop_monitor: perform u64_stats updates under IRQ-disabled section

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 54 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e9feb58020f952f7d9de785ede9a7d54ab1eda5c – < dd8472526a04f2185afd792b8041a912a7d75d85
    • affected e9feb58020f952f7d9de785ede9a7d54ab1eda5c – < 3454c729ee8aa682ec871f1b174b047f731933ae
    • affected e9feb58020f952f7d9de785ede9a7d54ab1eda5c – < be9b121894d6ad44f0011f79543a2e3245979497
    • affected e9feb58020f952f7d9de785ede9a7d54ab1eda5c – < 7d857cf5f0120bb0e020fa20b03bd21b9d3e0c04
    • affected e9feb58020f952f7d9de785ede9a7d54ab1eda5c – < d5e2cd2bc8ae36617346b3a54ee9da61d866bf92
    • affected e9feb58020f952f7d9de785ede9a7d54ab1eda5c – < fd098a23bf8fda7eae48db9b06e7c34fc4d228fa
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68286 badge
[![CVE-2026-68286](https://cveledger.app/badge/CVE-2026-68286.svg)](https://cveledger.app/cve/CVE-2026-68286)

Record last updated .