Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
39ba6af83a7f9dee3e6a7916f41a48bcbda54eba to < 42e3917cdbdc3d35e191c525687a6d5427f237fdaffected40e8b52fe8c8ab6920ea5f59c5469b6918cce624 to < cc848a080f7a6848dfeef441722419fdcbfe9b8daffected40e8b52fe8c8ab6920ea5f59c5469b6918cce624 to < 0bd5f2786a878148190b4c7c259d01313d5f2357affected40e8b52fe8c8ab6920ea5f59c5469b6918cce624 to < f3cf725cd284b7912d5522babb44721bf38c8887affected
Linux Linux
Default version status: affected
6.15affected0 to < 6.15unaffected6.18.40 to ≤ 6.18.*unaffected7.1.5 to ≤ 7.1.*unaffected7.2 to ≤ *unaffected