tipc: check for null after calling kmemdup
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 |
|
|
5.10.825.15.55.16In the Linux kernel, the following vulnerability has been resolved:
tipc: check for null after calling kmemdup
kmemdup can return a null pointer so need to check for it, otherwise the null key will be dereferenced later in tipc_crypto_key_xmit as can be seen in the trace [1].
[1] https://syzkaller.appspot.com/bug?id=bca180abb29567b189efdbdb34cbf7ba851c2a58
From the CVE record · Linux
In the Linux kernel, a failed kmemdup call can leave a null key that is later dereferenced in TIPC crypto key transmission, potentially causing a crash. The input does not specify how an attacker could trigger the failure or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their versions for this TIPC issue; affected versions are not specified.