In the Linux kernel, the following vulnerability has been resolved: afs: handle CB.InitCallBackState3 requests without a server record The cache manager callback path now attaches the server record to an incoming call through the rxrpc peer's app data. That association is not guaranteed to exist for every callback request, and most callback handlers already tolerate that case. Make CB.InitCallBackState3 follow the same pattern by checking whether a server record was attached before using it. If the peer is not mapped to a server record, trace the request and ignore it, matching the existing behaviour for other unmatched callback requests. This keeps the callback handler consistent with the rest of the cache manager service and avoids depending on peer state that may not be available for a given request.
https://git.kernel.org/stable/c/f3cf725cd284b7912d5522babb44721bf38c8887
https://git.kernel.org/stable/c/cc848a080f7a6848dfeef441722419fdcbfe9b8d
https://git.kernel.org/stable/c/42e3917cdbdc3d35e191c525687a6d5427f237fd
https://git.kernel.org/stable/c/0bd5f2786a878148190b4c7c259d01313d5f2357