CVE-2026-68286: drop_monitor: perform u64_stats updates under IRQ-disabled section
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 3454c729ee8aa682ec871f1b174b047f731933ae, 7d857cf5f0120bb0e020fa20b03bd21b9d3e0c04, be9b121894d6ad44f0011f79543a2e3245979497; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3454c729ee8aa682ec871f1b174b047f731933ae, 7d857cf5f0120bb0e020fa20b03bd21b9d3e0c04, be9b121894d6ad44f0011f79543a2e3245979497; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Aug 10, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.4affected
- e9feb58020f952f7d9de785ede9a7d54ab1eda5c and later · before dd8472526a04f2185afd792b8041a912a7d75d85affected · git
- e9feb58020f952f7d9de785ede9a7d54ab1eda5c and later · before 3454c729ee8aa682ec871f1b174b047f731933aeaffected · git
- e9feb58020f952f7d9de785ede9a7d54ab1eda5c and later · before be9b121894d6ad44f0011f79543a2e3245979497affected · git
- e9feb58020f952f7d9de785ede9a7d54ab1eda5c and later · before 7d857cf5f0120bb0e020fa20b03bd21b9d3e0c04affected · git
- e9feb58020f952f7d9de785ede9a7d54ab1eda5c and later · before d5e2cd2bc8ae36617346b3a54ee9da61d866bf92affected · git
- e9feb58020f952f7d9de785ede9a7d54ab1eda5c and later · before fd098a23bf8fda7eae48db9b06e7c34fc4d228faaffected · git
- before 5.4not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68274Aug 10, 2026 · drm/xe/guc: Fix buffer overflow in steered register list allocation31Monitor
- ← EarlierCVE-2026-68284Aug 10, 2026 · bpf, sockmap: Fix cork use-after-free in tcp_bpf_sendmsg()31Monitor
- Later →CVE-2026-68287Aug 10, 2026 · drop_monitor: fix size calculations for 64-bit attributes30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3454c729ee8aa682ec871f1b174b047f731933ae | Vendor (CNA) |
| Linux Linux | 7d857cf5f0120bb0e020fa20b03bd21b9d3e0c04 | Vendor (CNA) |
| Linux Linux | be9b121894d6ad44f0011f79543a2e3245979497 | Vendor (CNA) |
| Linux Linux | d5e2cd2bc8ae36617346b3a54ee9da61d866bf92 | Vendor (CNA) |
| Linux Linux | dd8472526a04f2185afd792b8041a912a7d75d85 | Vendor (CNA) |
| Linux Linux | fd098a23bf8fda7eae48db9b06e7c34fc4d228fa | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/7d857cf5f0120bb0e020fa20b03bd21b9d3e0c04
- git.kernel.org/stable/c/be9b121894d6ad44f0011f79543a2e3245979497
- git.kernel.org/stable/c/d5e2cd2bc8ae36617346b3a54ee9da61d866bf92
- git.kernel.org/stable/c/dd8472526a04f2185afd792b8041a912a7d75d85
- git.kernel.org/stable/c/fd098a23bf8fda7eae48db9b06e7c34fc4d228fa
Vendor advisories and official records. Exploit/PoC links are deliberately left out.