Race Condition Affecting kernel-64k-modules package, versions <0:5.14.0-284.11.1.el9_2


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.01% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Race Condition vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL9-KERNEL64KMODULES-10058881
  • published7 May 2025
  • disclosed27 Mar 2025

Introduced: 27 Mar 2025

CVE-2023-53020  (opens in a new tab)
CWE-362  (opens in a new tab)

How to fix?

Upgrade RHEL:9 kernel-64k-modules to version 0:5.14.0-284.11.1.el9_2 or higher.
This issue was patched in RHSA-2023:2458.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-64k-modules package and not the kernel-64k-modules package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

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().

CVSS Base Scores

version 3.1