CVEvulnerability
CVE-2023-53020
4.7 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2025-03-27
- Last modified
- 2026-06-17
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 ([email protected])
- 4.7 MEDIUM — CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
- CVSS 3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
- 4.7 MEDIUM — CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-362
Description
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().
Affected configurations
• linux linux kernel (>= 3.6 < 5.10.166)
• linux linux kernel (>= 5.11 < 5.15.91)
• linux linux kernel (>= 5.16 < 6.1.9)
• linux linux kernel 6.2
Related
Weakness · CWE (1)
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness
References
- https://git.kernel.org/stable/c/0b2c59720e65885a394a017d0cf9cab118914682 Patch
- https://git.kernel.org/stable/c/2d77e5c0ad79004b5ef901895437e9cce6dfcc7e Patch
- https://git.kernel.org/stable/c/77e8ed776cdb1a24b2aab8fe7c6f1f154235e1ce Patch
- https://git.kernel.org/stable/c/cef0845b6dcfa2f6c2c832e7f9622551456c741d Patch