l2tp: close all race conditions in l2tp_tunnel_register()
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
l2tp: close all race conditions in l2tp_tunnel_register()
The code in l2tp_tunnel_register() is racy in several ways:
1. It modifies the tunnel socket _after_ publishing it.
2. It calls setup_udp_tunnel_sock() on an existing socket without locking.
3. It changes sock lock class on fly, which triggers many syzbot reports.
This patch amends all of them by moving socket initialization code before publishing and under sock lock. As suggested by Jakub, the l2tp lockdep class is not necessary as we can just switch to bh_lock_sock_nested().
From the CVE record · Linux
The Linux kernel’s l2tp_tunnel_register() has race conditions involving tunnel socket initialization and locking. The input does not specify what an attacker could do or whether exploitation requires network access, authentication, local access, or user interaction.
Anyone running a Linux kernel with the affected L2TP code should check their version; affected versions are not specified.