uaccess: fix integer overflow on access_ok()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
uaccess: fix integer overflow on access_ok()
Three architectures check the end of a user access against the address limit without taking a possible overflow into account. Passing a negative length or another overflow in here returns success when it should not.
Use the most common correct implementation here, which optimizes for a constant 'size' argument, and turns the common case into a single comparison.
From the CVE record · Linux
On three Linux kernel architectures, access_ok() can incorrectly accept a user-memory access when its length is negative or causes an integer overflow. The input does not specify how an attacker could reach this check, or whether authentication or user interaction is required.
Engineers running the Linux kernel on affected architectures should check their deployments; affected versions are not specified.