io_uring/napi: cap busy_poll_to 10 msec
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.114, 6.18.33, 7.0.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: io_uring/napi: cap busy_poll_to 10 msec Currently there's no cap on the maximum amount of time that napi is allowed to poll if no events are found, which can lead to kernel complaints on a task being stuck as there's no conditional rescheduling done within that loop. Just cap it to 10 msec in total, that's already way above any kind of sane value that will reap any benefits, yet low enough that it's nowhere near being able to trigger preemption complaints.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 · fixed in 42785efe813e5a7d815f3b6be126e1bc0d12d2b6; From 8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 · fixed in 39767f944a8c9e696566c37ad5b20131406c4b8d; From 8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 · fixed in cb3af525f8dfb8930f0c123e5755fa967a12d5c1; From 8d0c12a80cdeb80d5e0510e96d38fe551ed8e9b5 · fixed in df8599ee18c0e5fe343ffe0b4c379636b8bb839a
- Linux Linux
6.9
- KernelLinux
From 6.9.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.33; From 6.19.0 · fixed in 7.0.10