CVE-2022-50174 json
net: hinic: avoid kernel hung in hinic_get_stats64()
published 2025-06-18 16 mo ago modified 2026-11-05 3 d ago also EUVD-2022-55439
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: hinic: avoid kernel hung in hinic_get_stats64()
When using hinic device as a bond slave device, and reading device stats of master bond device, the kernel may hung.
The kernel panic calltrace as follows: Kernel panic - not syncing: softlockup: hung tasks Call trace: native_queued_spin_lock_slowpath+0x1ec/0x31c dev_get_stats+0x60/0xcc dev_seq_printf_stats+0x40/0x120 dev_seq_show+0x1c/0x40 seq_read_iter+0x3c8/0x4dc seq_read+0xe0/0x130 proc_reg_read+0xa8/0xe0 vfs_read+0xb0/0x1d4 ksys_read+0x70/0xfc __arm64_sys_read+0x20/0x30 el0_svc_common+0x88/0x234 do_el0_svc+0x2c/0x90 el0_svc+0x1c/0x30 el0_sync_handler+0xa8/0xb0 el0_sync+0x148/0x180
And the calltrace of task that actually caused kernel hungs as follows: __switch_to+124 __schedule+548 schedule+72 schedule_timeout+348 __down_common+188 __down+24 down+104 hinic_get_stats64+44 [hinic] dev_get_stats+92 bond_get_stats+172 [bonding] dev_get_stats+92 dev_seq_printf_stats+60 dev_seq_show+24 seq_read_iter+964 seq_read+220 proc_reg_read+164 vfs_read+172 ksys_read+108 __arm64_sys_read+28 el0_svc_common+132 do_el0_svc+40 el0_svc+24 el0_sync_handler+164 el0_sync+324
When getting device stats from bond, kernel will call bond_get_stats(). It first holds the spinlock bond->stats_lock, and then call hinic_get_stats64() to collect hinic device's stats. However, hinic_get_stats64() calls `down(&nic_dev->mgmt_lock)` to protect its critical section, which may schedule current task out. And if system is under high pressure, the task cannot be woken up immediately, which eventually triggers kernel hung panic.
Since previous patch has replaced hinic_dev.tx_stats/rx_stats with local variable in hinic_get_stats64(), there is nothing need to be protected by lock, so just removing down()/up() is ok.
Patch / fix
- Linux Linux 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0
- linux Debian 14, Debian 13, Debian 12 6.0.2-1
debian advisories DEBIAN-CVE-2022-50174
- linux Ubuntu 22.04 LTS 5.15.0-53.59
- linux-aws Ubuntu 22.04 LTS 5.15.0-1023.27
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1022.29
- linux-gke Ubuntu 22.04 LTS 5.15.0-1020.25
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1018.21
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1021.26
- linux-azure Ubuntu 22.04 LTS 5.15.0-1023.29
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1008.12
ubuntu advisories UBUNTU-CVE-2022-50174
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/e74f3097a9c713ce855cda07713393bcc23a005d commit
- git.kernel.org/stable/c/693f31dc91568e61047fd2980a8235e856cd9ce8 commit
- git.kernel.org/stable/c/fced5bce712122654ec8a20356342698cce104d2 commit
- git.kernel.org/stable/c/3ba59bbe4f306bb6ee15753db0a40564c0eb7909 commit
- git.kernel.org/stable/c/98f9fcdee35add80505b6c73f72de5f750d5c03c commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50174 updated cvss 4.1
kernel: net: hinic: avoid kernel hung in hinic_get_stats64()
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
-
git.kernel.org
/stable/c/e74f3097a9c713ce855cda07713393bcc23a005d
patch
-
git.kernel.org
/stable/c/693f31dc91568e61047fd2980a8235e856cd9ce8
patch
-
git.kernel.org
/stable/c/fced5bce712122654ec8a20356342698cce104d2
patch
-
git.kernel.org
/stable/c/3ba59bbe4f306bb6ee15753db0a40564c0eb7909
patch
-
git.kernel.org
/stable/c/98f9fcdee35add80505b6c73f72de5f750d5c03c
patch
Sources
- CVE List CVE-2022-50174
- NVD CVE-2022-50174
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.