Answer in brief
CVE-2022-50676 records a High severity (CVSS 7.5) vulnerability in net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-50676 records a High severity (CVSS 7.5) vulnerability in net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <5d2ba255e93211e541373469dffbda7c99dfa0e5 || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <2425007c0967a7c04b0dee7cce05ecf0ca869ad1 || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <e3cb25d3ad08f5dbd53ce2b31720cad529944322 || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <360aa7219285fac63dab99706a16f2daf3222abe || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <da349221c4d2d4ac5f606c1c3b36d4ef0b3e6a0c || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <30bfa5aa7228eb1e67663d67e553627e572cc717 || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <c380c28ab9b15fc53565909c814f6dd3e7f77c4b || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <afe7053c390fe8ff27d0c2ceaece5625283044ba || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <a91b750fd6629354460282bbf5146c01b05c4859 | 5d2ba255e93211e541373469dffbda7c99dfa0e5, 2425007c0967a7c04b0dee7cce05ecf0ca869ad1, e3cb25d3ad08f5dbd53ce2b31720cad529944322, 360aa7219285fac63dab99706a16f2daf3222abe, da349221c4d2d4ac5f606c1c3b36d4ef0b3e6a0c, 30bfa5aa7228eb1e67663d67e553627e572cc717, c380c28ab9b15fc53565909c814f6dd3e7f77c4b, afe7053c390fe8ff27d0c2ceaece5625283044ba, a91b750fd6629354460282bbf5146c01b05c4859 |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Dec 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <5d2ba255e93211e541373469dffbda7c99dfa0e5 || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <2425007c0967a7c04b0dee7cce05ecf0ca869ad1 || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <e3cb25d3ad08f5dbd53ce2b31720cad529944322 || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <360aa7219285fac63dab99706a16f2daf3222abe || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <da349221c4d2d4ac5f606c1c3b36d4ef0b3e6a0c || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <30bfa5aa7228eb1e67663d67e553627e572cc717 || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <c380c28ab9b15fc53565909c814f6dd3e7f77c4b || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <afe7053c390fe8ff27d0c2ceaece5625283044ba || >=ac3615e7f3cffe2a1a6b25172dfd09e138593d82 <a91b750fd6629354460282bbf5146c01b05c4859 | 5d2ba255e93211e541373469dffbda7c99dfa0e5, 2425007c0967a7c04b0dee7cce05ecf0ca869ad1, e3cb25d3ad08f5dbd53ce2b31720cad529944322, 360aa7219285fac63dab99706a16f2daf3222abe, da349221c4d2d4ac5f606c1c3b36d4ef0b3e6a0c, 30bfa5aa7228eb1e67663d67e553627e572cc717, c380c28ab9b15fc53565909c814f6dd3e7f77c4b, afe7053c390fe8ff27d0c2ceaece5625283044ba, a91b750fd6629354460282bbf5146c01b05c4859 |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Dec 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.