cachefiles: unmark inode in use in error path
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:
cachefiles: unmark inode in use in error path
Unmark inode in use if error encountered. If the in-use flag leakage occurs in cachefiles_open_file(), Cachefiles will complain "Inode already in use" when later another cookie with the same index key is looked up.
If the in-use flag leakage occurs in cachefiles_create_tmpfile(), though the "Inode already in use" warning won't be triggered, fix the leakage anyway.
From the CVE record · Linux
The Linux kernel’s Cachefiles component can leave an inode marked in use after an error in cachefiles_open_file() or cachefiles_create_tmpfile(). A later lookup of another cookie with the same index key can trigger an “Inode already in use” warning. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels that use Cachefiles should check their versions; affected versions are not specified in the input.