block: don't revert iter for -EIOCBQUEUED
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
block: don't revert iter for -EIOCBQUEUED
blkdev_read_iter() has a few odd checks, like gating the position and count adjustment on whether or not the result is bigger-than-or-equal to zero (where bigger than makes more sense), and not checking the return value of blkdev_direct_IO() before doing an iov_iter_revert(). The latter can lead to attempting to revert with a negative value, which when passed to iov_iter_revert() as an unsigned value will lead to throwing a WARN_ON() because unroll is bigger than MAX_RW_COUNT.
Be sane and don't revert for -EIOCBQUEUED, like what is done in other spots.
From the CVE record · Linux
The Linux kernel’s blkdev_read_iter() can pass a negative return value from blkdev_direct_IO() to iov_iter_revert() as an unsigned value, triggering a WARN_ON(). The input does not specify how an attacker could trigger this, or whether network access, authentication, or user interaction is required.
Teams running the Linux kernel should check whether their versions are affected; the input does not identify affected versions.