In the Linux kernel, the following vulnerability has been resolved: cachefiles: defer exposing anon_fd until after copy_to_user() succeeds …
In the Linux kernel, the following vulnerability has been resolved: cachefiles: defer exposing anon_fd until after copy_to_user() succeeds After installing the anonymous fd, we can now see it in userland and close it. However, at this point we may not have gotten the reference count of the cache, but we will put it during colse fd, so this may cause a cache UAF. So grab the cache reference count before fd_install(). In addition, by kernel convention, fd is taken over by the user land after fd_install(), and the kernel should not call close_fd() after that, i.e., it should call fd_install() after everything is ready, thus fd_install() is called after copy_to_user() succeeds.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
https://cwe.mitre.org/data/definitions/416.html →Open in CWE collection →The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.
https://cwe.mitre.org/data/definitions/911.html →Open in CWE collection →| Product | Vendor | Status |
|---|---|---|
| kernel | Tracked | |
| kernel | Tracked | |
| linux | Tracked | |
| linux | Tracked | |
| linux | Tracked | |
| linux | Tracked | |
| linux | Tracked | |
| linux | Tracked | |
| linux | Tracked | |
| linux | Tracked | |
| linux | Tracked | |
| linux-6.1 | Tracked | |
| linux-6.1 | Tracked | |
| linux-6.1 | Tracked | |
| linux-allwinner-5.19 | Tracked | |
| linux-aws | Tracked | |
| linux-aws | Tracked | |
| linux-aws | Tracked | |
| linux-aws | Tracked | |
| linux-aws | Tracked |