io_uring/napi: make stale entries time out after 60s
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 18c373f446068972788158c8c7de6e849b04ed98, Kernel 3fe820cf35f83534eab72ea73f1a83cfd3cd8079, Kernel 981621d6eadcd232d4ea748aaeb046337f10d3c1 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 <18c373f446068972788158c8c7de6e849b04ed98, >=8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 <3fe820cf35f83534eab72ea73f1a83cfd3cd8079, >=8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 <981621d6eadcd232d4ea748aaeb046337f10d3c1, >=8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 <9c151648780d89e5446e5f89f3fa2e416c3bb911 | 18c373f446068972788158c8c7de6e849b04ed98, 3fe820cf35f83534eab72ea73f1a83cfd3cd8079, 981621d6eadcd232d4ea748aaeb046337f10d3c1, 9c151648780d89e5446e5f89f3fa2e416c3bb911 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket