afs: handle CB.InitCallBackState3 requests without a server record
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 42e3917cdbdc3d35e191c525687a6d5427f237fd, Kernel 0bd5f2786a878148190b4c7c259d01313d5f2357, Kernel cc848a080f7a6848dfeef441722419fdcbfe9b8d and 1 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.15, >=39ba6af83a7f9dee3e6a7916f41a48bcbda54eba <42e3917cdbdc3d35e191c525687a6d5427f237fd, >=40e8b52fe8c8ab6920ea5f59c5469b6918cce624 <0bd5f2786a878148190b4c7c259d01313d5f2357, >=40e8b52fe8c8ab6920ea5f59c5469b6918cce624 <cc848a080f7a6848dfeef441722419fdcbfe9b8d, >=40e8b52fe8c8ab6920ea5f59c5469b6918cce624 <f3cf725cd284b7912d5522babb44721bf38c8887 | 42e3917cdbdc3d35e191c525687a6d5427f237fd, 0bd5f2786a878148190b4c7c259d01313d5f2357, cc848a080f7a6848dfeef441722419fdcbfe9b8d, f3cf725cd284b7912d5522babb44721bf38c8887 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket