CVE-2022-50116

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-06-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

tty: n_gsm: fix deadlock and link starvation in outgoing data path

The current implementation queues up new control and user packets as needed and processes this queue down to the ldisc in the same code path. That means that the upper and the lower layer are hard coupled in the code. Due to this deadlocks can happen as seen below while transmitting data, especially during ldisc congestion. Furthermore, the data channels starve the control channel on high transmission load on the ldisc.

Introduce an additional control channel data queue to prevent timeouts and link hangups during ldisc congestion. This is being processed before the user channel data queue in gsm_data_kick(), i.e. with the highest priority. Put the queue to ldisc data path into a workqueue and trigger it whenever new data has been put into the transmission queue. Change gsm_dlci_data_sweep() accordingly to fill up the transmission queue until TX_THRESH_HI. This solves the locking issue, keeps latency low and provides good performance on high data load. Note that now all packets from a DLCI are removed from the internal queue if the associated DLCI was closed. This ensures that no data is sent by the introduced write task to an already closed DLCI.

BUG: spinlock recursion on CPU#0, test_v24_loop/124 lock: serial8250_ports+0x3a8/0x7500, .magic: dead4ead, .owner: test_v24_loop/124, .owner_cpu: 0 CPU: 0 PID: 124 Comm: test_v24_loop Tainted: G O 5.18.0-rc2 #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: dump_stack_lvl+0x34/0x44 do_raw_spin_lock+0x76/0xa0 _raw_spin_lock_irqsave+0x72/0x80 uart_write_room+0x3b/0xc0 gsm_data_kick+0x14b/0x240 [n_gsm] gsmld_write_wakeup+0x35/0x70 [n_gsm] tty_wakeup+0x53/0x60 tty_port_default_wakeup+0x1b/0x30 serial8250_tx_chars+0x12f/0x220 serial8250_handle_irq.part.0+0xfe/0x150 serial8250_default_handle_irq+0x48/0x80 serial8250_interrupt+0x56/0xa0 __handle_irq_event_percpu+0x78/0x1f0 handle_irq_event+0x34/0x70 handle_fasteoi_irq+0x90/0x1e0 __common_interrupt+0x69/0x100 common_interrupt+0x48/0xc0 asm_common_interrupt+0x1e/0x40 RIP: 0010:__do_softirq+0x83/0x34e Code: 2a 0a ff 0f b7 ed c7 44 24 10 0a 00 00 00 48 c7 c7 51 2a 64 82 e8 2d e2 d5 ff 65 66 c7 05 83 af 1e 7e 00 00 fb b8 ff ff ff ff <49> c7 c2 40 61 80 82 0f bc c5 41 89 c4 41 83 c4 01 0f 84 e6 00 00 RSP: 0018:ffffc90000003f98 EFLAGS: 00000286 RAX: 00000000ffffffff RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff82642a51 RDI: ffffffff825bb5e7 RBP: 0000000000000200 R08: 00000008de3271a8 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000030 R14: 0000000000000000 R15: 0000000000000000 ? __do_softirq+0x73/0x34e irq_exit_rcu+0xb5/0x100 common_interrupt+0xa4/0xc0 asm_common_interrupt+0x1e/0x40 RIP: 0010:_raw_spin_unlock_irqrestore+0x2e/0x50 Code: 00 55 48 89 fd 48 83 c7 18 53 48 89 f3 48 8b 74 24 10 e8 85 28 36 ff 48 89 ef e8 cd 58 36 ff 80 e7 02 74 01 fb bf 01 00 00 00 3d 97 33 ff 65 8b 05 96 23 2b 7e 85 c0 74 03 5b 5d c3 0f 1f 44 RSP: 0018:ffffc9000020fd08 EFLAGS: 00000202 RAX: 0000000000000000 RBX: 0000000000000246 RCX: 0000000000000000 RDX: 0000000000000004 RSI: ffffffff8257fd74 RDI: 0000000000000001 RBP: ffff8880057de3a0 R08: 00000008de233000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000100 R14: 0000000000000202 R15: ffff8880057df0b8 ? _raw_spin_unlock_irqrestore+0x23/0x50 gsmtty_write+0x65/0x80 [n_gsm] n_tty_write+0x33f/0x530 ? swake_up_all+0xe0/0xe0 file_tty_write.constprop.0+0x1b1/0x320 ? n_tty_flush_buffer+0xb0/0xb0 new_sync_write+0x10c/0x190 vfs_write+0x282/0x310 ksys_write+0x68/0xe0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f3e5e35c15c Code: 8b 7c 24 08 89 c5 e8 c5 ff ff ff 89 ef 89 44 24 ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 18, 2025

Last Modified

June 1, 2026

References (4)

Vendor Advisories for CVE-2022-50116(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-553.el8_102024-05-22redhat
redhatkernel-0:4.18.0-477.55.1.el8_82024-04-30redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 5.15.209 (fixes >=2.6.35)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.19.6-1: fixed in 5.19.6-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.19.6-1: fixed in 5.19.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.19.6-1: fixed in 5.19.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 92 of 162 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 70 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-18 08:19 UTCEG score recompute
  8. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-12 18:41 UTCEG score recompute
  14. 2026-10-11 22:04 UTCEG score recompute
  15. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-02 11:11 UTCOSV refresh
  25. 2026-09-30 16:13 UTCEG score recompute
Show 67 more
  1. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  7. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  8. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-09-13 09:24 UTCOSV refresh
  13. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-08-25 10:11 UTCOSV refresh
  30. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-08-09 02:52 UTCOSV refresh
  43. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  45. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  47. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  49. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  51. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  52. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  53. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  55. 2026-07-24 03:11 UTCOSV refresh
  56. 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  57. 2026-07-23 02:16 UTCEG score recompute
  58. 2026-07-22 23:04 UTCEG score recompute
  59. 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  60. 2026-07-21 15:23 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  61. 2026-07-20 17:05 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  62. 2026-07-19 14:29 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  63. 2026-07-18 10:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  64. 2026-07-16 17:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  65. 2026-07-15 16:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  66. 2026-07-15 01:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  67. 2026-07-13 22:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-50116?
CVE-2022-50116 is a medium-severity vulnerability; its CVE record was published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix deadlock and link starvation in outgoing data path The current implementation queues up new control and user packets as needed and processes this queue down to the ldisc in the same code path. That means that the…
When was the CVE record for CVE-2022-50116 published?
The CVE record for CVE-2022-50116 was published on June 18, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 1, 2026; the record at its source may have been updated since.
Is CVE-2022-50116 actively exploited?
CVE-2022-50116 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50116?
CVE-2022-50116 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50116?
A fix for CVE-2022-50116 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50116 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50116

Explore →

Is Your Infrastructure Affected by CVE-2022-50116?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs