Answer in brief
CVE-2026-23313 records a Unknown severity vulnerability in i40e: Fix preempt count leak in napi poll tracepoint. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6d4d584a7ea8fc8d2be77545cb503118c193738a <fa5d5baf67f619c7aa70697a194b5a9edd9f5bb7 || >=6d4d584a7ea8fc8d2be77545cb503118c193738a <b7e91827e1cf89cd34ad11dc8f8c010b70ab786e || >=6d4d584a7ea8fc8d2be77545cb503118c193738a <9e0f091821571f0da387462803ee42f0bb157582 || >=6d4d584a7ea8fc8d2be77545cb503118c193738a <dca4ea596a3b0a1b82bc1d9f3e4d88bd9ad9561f || >=6d4d584a7ea8fc8d2be77545cb503118c193738a <4b3d54a85bd37ebf2d9836f0d0de775c0ff21af9 | fa5d5baf67f619c7aa70697a194b5a9edd9f5bb7, b7e91827e1cf89cd34ad11dc8f8c010b70ab786e, 9e0f091821571f0da387462803ee42f0bb157582, dca4ea596a3b0a1b82bc1d9f3e4d88bd9ad9561f, 4b3d54a85bd37ebf2d9836f0d0de775c0ff21af9 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Mar 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: i40e: Fix preempt count leak in napi poll tracepoint Using get_cpu() in the tracepoint assignment causes an obvious preempt count leak because nothing invokes put_cpu() to undo it: softirq: huh, entered softirq 3 NET_RX with preempt_count 00000100, exited with 00000101? This clearly has seen a lot of testing in the last 3+ years... Use smp_processor_id() instead.
Quoted source text, attributed separately from HOL analysis.