CVE-2024-53047

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+.