CVE-2022-50676: net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks()
In the Linux kernel, the following vulnerability has been resolved:
net: rds: don't hold sock lock when cancelling work from rdstcpresetcallbacks()
syzbot is reporting lockdep warning at rdstcpresetcallbacks() [1], for commit ac3615e7f3cffe2a ("RDS: TCP: Reduce code duplication in rdstcpresetcallbacks()") added canceldelayedworksync() into a section protected by locksock() without realizing that rdssendxmit() might call locksock().
We don't need to protect canceldelayedworksync() using locksock(), for even if rds{send,recv}worker() re-queued this work while flushwork() from canceldelayedworksync() was waiting for this work to complete, retried rds{send,recv}worker() is no-op due to the absence of RDSCONNUP bit.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2022-50676?
CVE-2022-50676 has not been assigned a specific CVSS score, but it is a security issue that can affect system stability.
How do I fix CVE-2022-50676?
To resolve CVE-2022-50676, update to the latest version of the Linux kernel where the vulnerability has been patched.
What are the potential impacts of CVE-2022-50676?
CVE-2022-50676 can lead to lockdep warnings, potentially affecting system reliability.
Which systems are affected by CVE-2022-50676?
CVE-2022-50676 affects systems running vulnerable versions of the Linux kernel that utilize RDS over TCP.
Is CVE-2022-50676 being actively exploited?
As of now, there are no reports of active exploitation for CVE-2022-50676.