afs: Fix the locking used by afs_get_link()
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 |
|
|
6.18.577.0.117.1In the Linux kernel, the following vulnerability has been resolved:
afs: Fix the locking used by afs_get_link()
The afs filesystem in the kernel doesn't do locking correctly for symbolic links. There are a number of problems:
(1) It doesn't do any locking around afs_read_single() to prevent races between multiple ->get_link() calls, thereby allowing the possibility of leaks.
(2) It doesn't use RCU barriering when accessing the buffer pointers during RCU pathwalk.
(3) It can race with another thread updating the contents of the symlink if a third party updated it on the server.
Fix this by the following means:
(0) Move symlink handling into its own file as this makes it more complicated.
From the CVE record · Linux
The Linux kernel's AFS filesystem does not lock or synchronize symbolic-link access correctly. Concurrent symlink lookups can cause leaks, and lookups can race with a symlink update by a third party on the server; the input does not specify authentication requirements.
Engineers running Linux kernels with the AFS filesystem should check their kernel versions against the vendor advisory; affected versions are not specified.