Review reviewHigh

CVE-2022-50676

Linux

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

CVSS
7.5
EPSS
0.85%
54.7% percentile
CISA KEV
Not listed
Published
2025.12.10
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.85%
Technical severityCVSS 7.5

Vulnerability overview

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

Affected product and versions

Product
Linux
Affected versions
>= ac3615e7f3cffe2a1a6b25172dfd09e138593d82 < 5d2ba255e93211e541373469dffbda7c99dfa0e5, >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82 < 2425007c0967a7c04b0dee7cce05ecf0ca869ad1, >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82 < e3cb25d3ad08f5dbd53ce2b31720cad529944322, >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82 < 360aa7219285fac63dab99706a16f2daf3222abe, >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82 < da349221c4d2d4ac5f606c1c3b36d4ef0b3e6a0c, >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82 < 30bfa5aa7228eb1e67663d67e553627e572cc717, >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82 < c380c28ab9b15fc53565909c814f6dd3e7f77c4b, >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82 < afe7053c390fe8ff27d0c2ceaece5625283044ba, >= ac3615e7f3cffe2a1a6b25172dfd09e138593d82 < a91b750fd6629354460282bbf5146c01b05c4859, >= 4.8
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE
Not available
CVE-2022-50676 — Linux | SECUFOCUS NOW