rxrpc: Fix oops due to non-existence of prealloc backlog struct
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 248f219cb8bcbfbd7f132752d44afa2df7c241d1 · < d1ff5f9d2c5405681457262e23c720b08977c11f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix oops due to non-existence of prealloc backlog struct
If an AF_RXRPC service socket is opened and bound, but calls are preallocated, then rxrpc_alloc_incoming_call() will oops because the rxrpc_backlog struct doesn't get allocated until the first preallocation is made.
Fix this by returning NULL from rxrpc_alloc_incoming_call() if there is no backlog struct. This will cause the incoming call to be aborted.
From the CVE record · Linux
An incoming call to an opened and bound AF_RXRPC service socket can cause a kernel oops if its preallocation backlog structure has not been allocated. The input does not specify authentication or user-interaction requirements.
Anyone running the Linux kernel should check their version against the vendor advisory; affected versions are not specified here.