CVE-2026-99267
io_uring/napi: make stale entries time out after 60s
In the Linux kernel, the following vulnerability has been resolved: io_uring/napi: make stale entries time out after 60s With dynamic tracking a NAPI id that hasn't been seen for a minute is meant to be dropped from the list the ring busy polls. The timeout is added to jiffies, but it is defined as 60 * SEC_CONVERSION, and SEC_CONVERSION isn't the number of jiffies in a second. It is the internal factor of __timespec64_to_jiffies(), HZ scaled up by SEC_JIFFIE_SC bits. For HZ=1000 that is 1000 << 22, which puts the timeout at about eight years. On 32-bit the multiplication overflows. So entries are never removed, and every id that a socket of the ring ever had keeps being polled on each wait.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5; < 3fe820cf35f83534eab72ea73f1a83cfd3cd8079 (affected, git) ≥ 8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5; < 18c373f446068972788158c8c7de6e849b04ed98 (affected, git) ≥ 8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5; < 981621d6eadcd232d4ea748aaeb046337f10d3c1 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
6.9 (affected) ≥ 0; < 6.9 (unaffected, semver) ≥ 6.12.115; ≤ 6.12.* (unaffected, semver) ≥ 6.18.60; ≤ 6.18.* (unaffected, semver) ≥ 7.2.14; ≤ 7.2.* (unaffected, semver) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.