LiveActive security incident?Get immediate response
CVE Record

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel issue in the RDS over TCP networking code. A locking mistake could cause kernel work cancellation to wait while holding a socket lock, creating an availability risk under relevant RDS/TCP conditions. Public sources do not provide a CVSS score or evidence of active exploitation.

Executive priority

Schedule remediation through normal kernel patch cycles, with higher priority for systems using RDS/TCP or sensitive availability workloads. There is no sourced evidence of active exploitation, but kernel availability defects can still have operational impact.

Technical view

The fix moves cancel_delayed_work_sync() outside a lock_sock()-protected section in rds_tcp_reset_callbacks(). The CVE notes syzbot reported a lockdep warning after commit ac3615e7f3cffe2a added cancellation inside the locked section, while rds_send_xmit() may also call lock_sock().

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the RDS/TCP code present and reachable in their workload. Systems not using RDS/TCP are less likely to encounter the vulnerable path, but package-level exposure still depends on distribution kernel backports.

Exploitation context

The provided sources describe a syzbot-discovered locking problem and stable kernel fixes. They do not report public exploitation, weaponized proof-of-concept activity, or CISA KEV listing. Treat this primarily as a kernel availability and reliability issue unless vendor advisories indicate otherwise.

Researcher notes

Evidence is limited to the CVE record and upstream stable commits. No CVSS, CWE, exploit status, or distribution-specific advisories are included. Validate affectedness through kernel commit ancestry or vendor backport data rather than version strings alone.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check distribution advisories for backported fixes and supported kernel package names.
  • Prioritize systems that use or expose RDS/TCP functionality.
  • If patch timing is unclear, request vendor guidance before applying compensating controls.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and cloud images.
  • Map installed vendor kernels to the stable commits or distribution advisories.
  • Confirm whether RDS/TCP functionality is enabled or required in relevant environments.
  • After updating, verify the running kernel is the patched vendor build.
Prepared
Confidence
medium
Sources
11

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50676 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxac3615e7f3cffe2a1a6b25172dfd09e138593d82, ac3615e7f3cffe2a1a6b25172dfd09e138593d82, ac3615e7f3cffe2a1a6b25172dfd09e138593d82, ac3615e7f3cffe2a1a6b25172dfd09e138593d82, ac3615e7f3cffe2a1a6b25172dfd09e138593d82, ac3615e7f3cffe2a1a6b25172dfd09e138593d82, ac3615e7f3cffe2a1a6b25172dfd09e138593d82, ac3615e7f3cffe2a1a6b25172dfd09e138593d82, ac3615e7f3cffe2a1a6b25172dfd09e138593d82unaffected
LinuxLinux4.8, 0, 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.