atm: clip: Fix potential null-ptr-deref in to_atmarpd().
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 36caab990b69ef4eec1d81c52a19f080b7daa059| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
atm: clip: Fix potential null-ptr-deref in to_atmarpd().
atmarpd is protected by RTNL since commit f3a0592b37b8 ("[ATM]: clip causes unregister hang").
However, it is not enough because to_atmarpd() is called without RTNL, especially clip_neigh_solicit() / neigh_ops->solicit() is unsleepable.
Also, there is no RTNL dependency around atmarpd.
Let's use a private mutex and RCU to protect access to atmarpd in to_atmarpd().
From the CVE record · Linux
The Linux kernel’s ATM CLIP code can dereference a null pointer in to_atmarpd() because access to atmarpd is not adequately protected. The input does not specify how an attacker could trigger this or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check for this issue; affected versions are not specified.