Excess CPU work via incorrect NAPI expiration
Published Nov 3, 2026 · Updated Nov 3, 2026
Incorrect NAPI expiry in Linux io_uring allows local users to cause repeated polling of stale socket IDs and excess CPU work. In io_uring/napi.c, NAPI_TIMEOUT uses 60 * SEC_CONVERSION instead of a jiffies-based duration, retaining entries far beyond the intended minute and overflowing the multiplication on 32-bit systems. Exposure requires CONFIG_NET_RX_BUSY_POLL and dynamic NAPI tracking on an active ring; the documented consequence is unnecessary polling, not a demonstrated crash or reboot.
Summary
What happened
Incorrect NAPI expiry in Linux io_uring allows local users to cause repeated polling of stale socket IDs and excess CPU work. In io_uring/napi.c, NAPI_TIMEOUT uses 60 * SEC_CONVERSION instead of a jiffies-based duration, retaining entries far beyond the intended minute and overflowing the multiplication on 32-bit systems. Exposure requires CONFIG_NET_RX_BUSY_POLL and dynamic NAPI tracking on an active ring; the documented consequence is unnecessary polling, not a demonstrated crash or reboot.
The record
- CVE
- CVE-2026-99267
- Published
- Nov 3, 2026
- Updated
- Nov 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 3, 2026CVE publishedPublication date reported by the CVE source.
- Nov 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.9
- Affected versionversion=8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 <18c373f446068972788158c8c7de6e849b04ed98
- Affected versionversion=8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 <3fe820cf35f83534eab72ea73f1a83cfd3cd8079
- Affected versionversion=8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 <981621d6eadcd232d4ea748aaeb046337f10d3c1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us