CVE-2022-50676

HIGHCVSS 7.5/10EPSS 0.25%

Last modified

CVE-2022-50676 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks() syzbot is reporting lockdep warning at rds_tcp_reset_callbacks() [1], for commit ac3615e7f3cffe2a ("RDS: TCP: Reduce code duplication in rds_tcp_reset_callbacks()") added cancel_delayed_work_sync() into a section protected by lock_sock() without realizing that rds_send_xmit() might call lock_sock(). We don't need to protect cancel_delayed_work_sync() using lock_sock(), for even if rds_{send,recv}_worker() re-queued this work while __flush_work() from cancel_delayed_work_sync() was waiting for this work to complete, retried rds_{send,recv}_worker() is no-op due to the absence of RDS_CONN_UP bit.. EPSS estimates a 0.25% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks() syzbot is reporting lockdep warning at rds_tcp_reset_callbacks() [1], for commit ac3615e7f3cffe2a ("RDS: TCP: Reduce code duplication in rds_tcp_reset_callbacks()") added cancel_delayed_work_sync() into a section protected by lock_sock() without realizing that rds_send_xmit() might call lock_sock(). We don't need to protect cancel_delayed_work_sync() using lock_sock(), for even if rds_{send,recv}_worker() re-queued this work while __flush_work() from cancel_delayed_work_sync() was waiting for this work to complete, retried rds_{send,recv}_worker() is no-op due to the absence of RDS_CONN_UP bit.

Metrics

CVSS 3.1
7.5/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS Probability
0.25%

16.9th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ac3615e7f3cffe2a1a6b25172dfd09e138593d82, < 5d2ba255e93211e541373469dffbda7c99dfa0e5; >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82, < 2425007c0967a7c04b0dee7cce05ecf0ca869ad1; >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82, < e3cb25d3ad08f5dbd53ce2b31720cad529944322; >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82, < 360aa7219285fac63dab99706a16f2daf3222abe; >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82, < da349221c4d2d4ac5f606c1c3b36d4ef0b3e6a0c; >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82, < 30bfa5aa7228eb1e67663d67e553627e572cc717; >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82, < c380c28ab9b15fc53565909c814f6dd3e7f77c4b; >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82, < afe7053c390fe8ff27d0c2ceaece5625283044ba; >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82, < a91b750fd6629354460282bbf5146c01b05c4859
LinuxLinux4.8

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2022-50676?
In the Linux kernel, the following vulnerability has been resolved: net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks() syzbot is reporting lockdep warning at rds_tcp_reset_callbacks() [1], for commit ac3615e7f3cffe2a ("RDS: TCP: Reduce code duplication in rds_tcp_reset_callbacks()") added cancel_delayed_work_sync() into a section protected by lock_sock() without realizing that rds_send_xmit() might call lock_sock(). We don't need to protect cancel_delayed_work_sync() using lock_sock(), for even if rds_{send,recv}_worker() re-queued this work while __flush_work() from cancel_delayed_work_sync() was waiting for this work to complete, retried rds_{send,recv}_worker() is no-op due to the absence of RDS_CONN_UP bit.
How severe is CVE-2022-50676?
CVE-2022-50676 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 0.25% probability of exploitation in the next 30 days.
How do I fix CVE-2022-50676?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2022

Are you affected by CVE-2022-50676?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST