PT-2024-35512 · Linux+4 · Linux Kernel+4
Published
2024-10-21
·
Updated
2025-10-03
·
CVE-2024-53047
CVSS v3.1
5.5
Medium
| Vector | AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Name of the Vulnerable Software and Affected Versions
Linux kernel versions prior to 6.12.0-rc2+
Description
The issue arises when the socket is initialized without using
rcu read lock(), despite an explicit comment above the declaration of mptcp sched find() in sched.c. This results in a warning about suspicious RCU usage when an MPTCP socket is created. The problem occurs when CONFIG PROVE RCU LIST is enabled with its dependence CONFIG RCU EXPERT. The warning is triggered by the lockdep rcu suspicious function and is followed by a stack backtrace.Recommendations
To resolve the issue, add the missing
rcu read lock() and rcu read unlock() around the mptcp sched find() function call in sched.c. This will protect the scheduler with rcu read lock() and avoid the warning.Note: The provided information does not specify the exact version where the issue is fixed, only that it is resolved in versions after 6.12.0-rc2+.
Exploit
Fix
Improper Locking
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Alt Linux
Linuxmint
Linux Kernel
Red Hat
Ubuntu