References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

Change History

In the Linux kernel, the following vulnerability has been resolved:

rxrpc: Only put the call ref if one was acquired

rxrpc_input_packet_on_conn() can process a to-client packet after the
current client call on the channel has already been torn down.  In that
case chan->call is NULL, rxrpc_try_get_call() returns NULL and there is
no reference to drop.

The client-side implicit-end error path does not account for that and
unconditionally calls rxrpc_put_call().  This turns a protocol error
path into a kernel crash instead of rejecting the packet.

Only drop the call reference if one was actually acquired.  Keep the
existing protocol error handling unchanged.

https://git.kernel.org/stable/c/0c156aff8a2d4fa0d61db7837641975cf0e5452d

https://git.kernel.org/stable/c/6331f1b24a3e85465f6454e003a3e6c22005a5c5

https://git.kernel.org/stable/c/8299ca146489664e3c0c90a3b8900d8335b1ede4

https://git.kernel.org/stable/c/9fb09861e2b8d1abfe2efaf260c9f1d30080ea38

https://git.kernel.org/stable/c/b8f66447448d6c305a51413a67ec8ed26aa7d1dd