Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50116: tty: n_gsm: fix deadlock and link starvation in outgoing data path

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0af021678d5d30c31f5a6b631f404ead3575212a, 5020173e7e7725110a8d4be1359bf1dfc4b1814d, 7962a4b900099cf90e02859bb297f2c618d8d940.

Low priority for now. Upgrade to Linux Linux 0af021678d5d30c31f5a6b631f404ead3575212a, 5020173e7e7725110a8d4be1359bf1dfc4b1814d, 7962a4b900099cf90e02859bb297f2c618d8d940 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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: <IRQ> 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 </IRQ> <TASK> 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 <e8> 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---

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 18, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-50116

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.35 and later · before 5.18.18
  • linux linux kernel5.19 and later · before 5.19.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.35affected
    • e1eaea46bb4020b38a141b84f88565d4603f8dd0 and later · before 5020173e7e7725110a8d4be1359bf1dfc4b1814daffected · git
    • e1eaea46bb4020b38a141b84f88565d4603f8dd0 and later · before c165698c9919b000bdbe73859d3bb7b33bdb9223affected · git
    • e1eaea46bb4020b38a141b84f88565d4603f8dd0 and later · before 7962a4b900099cf90e02859bb297f2c618d8d940affected · git
    • e1eaea46bb4020b38a141b84f88565d4603f8dd0 and later · before 0af021678d5d30c31f5a6b631f404ead3575212aaffected · git
    • before 2.6.35not affected · semver
    • 5.15.209 and later · up to and including 5.15.*not affected · semver
    • 5.18.18 and later · up to and including 5.18.*not affected · semver
    • 5.19.2 and later · up to and including 5.19.*not affected · semver
    • 6.0 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.19.6-15.19.6-1
Red Hat:enterprise_linux:8::baseosbpftoolbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseosbpftool-debuginfobefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernelbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-abi-stablelistsbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-corebefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debugbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-corebefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-debuginfobefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-develbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-modulesbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-modules-extrabefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfobefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-develbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-docbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-modulesbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-modules-extrabefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-toolsbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-tools-debuginfobefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-tools-libsbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-50114Jun 18, 2025 · net: 9p: fix refcount leak in p9_read_work() error handling
    22Monitor
  • ← EarlierCVE-2022-50115Jun 18, 2025 · ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes
    31Monitor
  • Later →CVE-2022-50117Jun 18, 2025 · vfio: Split migration ops from main device ops
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0af021678d5d30c31f5a6b631f404ead3575212aVendor (CNA)
Linux Linux5020173e7e7725110a8d4be1359bf1dfc4b1814dVendor (CNA)
Linux Linux7962a4b900099cf90e02859bb297f2c618d8d940Vendor (CNA)
Linux Linuxc165698c9919b000bdbe73859d3bb7b33bdb9223Vendor (CNA)
debian:linux5.19.6-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:4.18.0-553.123.1.el8_10.cloud.0.1 · Rocky Linux:8Package registry (OSV)
suse:kernel-64kb5.3.18-150300.59.218.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-default4.12.14-122.272.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-default-base5.3.18-150300.59.218.1.150300.18.130.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-docs5.3.18-150300.59.218.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP3_Update_611-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-obs-build5.3.18-150300.59.218.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150300.59.218.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-rt5.14.21-150500.13.106.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-source4.12.14-122.272.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-source-rt5.14.21-150500.13.106.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-syms4.12.14-122.272.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_721-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records