CVE-2026-23313
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A preempt count leak in the i40e40e's NAPI poll tracepoint, caused by get_cpu() without put_cpu(), leads to kernel softirq warnings.
Vulnerability
In the Linux kernel's i40e network driver, the NAPI poll tracepoint incorrectly uses get_cpu() to obtain the current CPU number without a corresponding put_cpu() call. This creates a preempt count leak, as the preemption counter is incremented but never decremented [1]. The kernel's softirq handler detects the mismatch and logs a warning such as: "softirq: huh, entered softirq 3 NET_RX with preempt_count 00000100, exited with 00000101?" [1].
Exploitation
This bug is triggered during normal network packet processing when the i40e devices. No special privileges or network position are required; any network traffic handled by the driver can cause the tracepoint to fire and leak the preempt count. The issue has existed for over three years, indicating it has been present in many kernel versions [1].
Impact
The primary impact is a kernel warning message and a corrupted preempt count, which can lead to unpredictable behavior in preemption-sensitive code paths. While not directly exploitable for privilege escalation or remote code execution, the warning indicates a kernel state inconsistency that could contribute to instability or denial-of-service conditions.
Mitigation
The fix replaces get_cpu() with smp_processor_id(), which does not modify the preempt count [1]. Patched versions are available in the stable kernel tree [1][2][3][4]. Users should update to a kernel containing the fix.
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
5- git.kernel.org/stable/c/4b3d54a85bd37ebf2d9836f0d0de775c0ff21af9nvd
- git.kernel.org/stable/c/9e0f091821571f0da387462803ee42f0bb157582nvd
- git.kernel.org/stable/c/b7e91827e1cf89cd34ad11dc8f8c010b70ab786envd
- git.kernel.org/stable/c/dca4ea596a3b0a1b82bc1d9f3e4d88bd9ad9561fnvd
- git.kernel.org/stable/c/fa5d5baf67f619c7aa70697a194b5a9edd9f5bb7nvd
News mentions
0No linked articles in our index yet.