afs: handle CB.InitCallBackState3 requests without a server record
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:
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.
From the CVE record · Linux
The Linux kernel AFS callback handler can use a missing server record when it receives a CB.InitCallBackState3 request from an rxrpc peer not mapped to a server record. The description does not specify the resulting impact, authentication requirements, or whether user interaction is needed.
Teams running Linux kernels with the AFS cache manager should check their installations; affected versions were not provided.