In the Linux kernel, the following vulnerability has been resolved:
io_uring: check if we need to reschedule during overflow flush
In terms of normal application usage, this list will always be empty.
And if an application does overflow a bit, it'll have a few entries.
However, nothing obviously prevents syzbot from running a test case
that generates a ton of overflow entries, and then flushing them can
take quite a while.
Check for needing to reschedule while flushing, and drop our locks and
do so if necessary. There's no state to maintain here as overflows
always prune from head-of-list, hence it's fine to drop and reacquire
the locks at the end of the loop.
References
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2024-10-21 20:15
Updated : 2024-11-20 20:25
NVD link : CVE-2024-50060
Mitre link : CVE-2024-50060
CVE.ORG link : CVE-2024-50060
JSON object : View
Products Affected
linux
- linux_kernel
CWE