LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23313: i40e: Fix preempt count leak in napi poll tracepoint

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23313 is a Linux kernel issue in the i40e network driver. A tracepoint used the wrong CPU helper and could leave the kernel preemption counter unbalanced. The sources do not provide CVSS, CWE, exploitability, or business-impact details, so urgency should be based on kernel exposure and vendor guidance.

Executive priority

Handle through normal kernel patch governance unless local exposure is high. Escalate priority for critical network infrastructure using i40e once vendor packages confirm affected builds.

Technical view

The resolved flaw is a preempt count leak in the i40e NAPI poll tracepoint. The description says get_cpu() was used in tracepoint assignment without a matching put_cpu(), producing a softirq preempt_count mismatch. The fix changes this to smp_processor_id().

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the i40e driver path relevant. The bundle lists Linux as affected and references stable kernel commits, but it does not identify specific distributions, hardware inventories, or default driver-loading conditions.

Exploitation context

No active exploitation is indicated. The KEV flag is false, and the provided sources do not describe public exploitation, exploit prerequisites, or attacker-controlled impact. Treat exploitability as unproven from this bundle.

Researcher notes

Evidence is narrow: the CVE text identifies the flawed helper, observed softirq preempt_count mismatch, and stable fix commits. It does not supply CVSS, CWE, proof of exploitation, affected distributions, or a standalone mitigation.

Mitigation direction

  • Apply distribution kernel updates that include the referenced stable fixes.
  • Prioritize Linux hosts using the i40e network driver.
  • Track vendor advisories for affected kernel branches and backports.
  • If updates are unavailable, request vendor guidance for interim mitigation.

Validation and detection

  • Inventory kernel versions across Linux assets.
  • Identify systems where the i40e driver is loaded or required.
  • Map installed kernels to vendor advisories and referenced stable commits.
  • Confirm patched kernels are running after maintenance windows.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23313 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6d4d584a7ea8fc8d2be77545cb503118c193738a, 6d4d584a7ea8fc8d2be77545cb503118c193738a, 6d4d584a7ea8fc8d2be77545cb503118c193738a, 6d4d584a7ea8fc8d2be77545cb503118c193738a, 6d4d584a7ea8fc8d2be77545cb503118c193738aunaffected
LinuxLinux6.2, 0, 6.6.136, 6.12.77, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.