Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fa5d5baf67f619c7aa70697a194b5a9edd9f5bb7 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 22:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in fa5d5baf67f619c7aa70697a194b5a9edd9f5bb7, dca4ea596a3b0a1b82bc1d9f3e4d88bd9ad9561f, b7e91827e1cf89cd34ad11dc8f8c010b70ab786e +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 6d4d584a7ea8fc8d2be77545cb503118c193738a, < fa5d5baf67f619c7aa70697a194b5a9edd9f5bb7
Fixed in
  • fa5d5baf67f619c7aa70697a194b5a9edd9f5bb7
LinuxLinuxAffected
  • ≥ 6d4d584a7ea8fc8d2be77545cb503118c193738a, < dca4ea596a3b0a1b82bc1d9f3e4d88bd9ad9561f
Fixed in
  • dca4ea596a3b0a1b82bc1d9f3e4d88bd9ad9561f
LinuxLinuxAffected
  • ≥ 6d4d584a7ea8fc8d2be77545cb503118c193738a, < b7e91827e1cf89cd34ad11dc8f8c010b70ab786e
Fixed in
  • b7e91827e1cf89cd34ad11dc8f8c010b70ab786e
LinuxLinuxAffected
  • ≥ 6d4d584a7ea8fc8d2be77545cb503118c193738a, < 9e0f091821571f0da387462803ee42f0bb157582
Fixed in
  • 9e0f091821571f0da387462803ee42f0bb157582
LinuxLinuxAffected
  • ≥ 6d4d584a7ea8fc8d2be77545cb503118c193738a, < 4b3d54a85bd37ebf2d9836f0d0de775c0ff21af9
Fixed in
  • 4b3d54a85bd37ebf2d9836f0d0de775c0ff21af9
LinuxLinuxAffected
  • =6.2
Fixed in–

Description

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.

References

Community reviews

Loading reviews…