LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50171: crypto: hisilicon/sec - don't sleep when in softirq

In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/sec - don't sleep when in softirq When kunpeng920 encryption driver is used to deencrypt and decrypt packets during the softirq, it is not allowed to use mutex lock. The kernel will report the following error: BUG: scheduling while atomic: swapper/57/0/0x00000300 Call trace: dump_backtrace+0x0/0x1e4 show_stack+0x20/0x2c dump_stack+0xd8/0x140 __schedule_bug+0x68/0x80 __schedule+0x728/0x840 schedule+0x50/0xe0 schedule_preempt_disabled+0x18/0x24 __mutex_lock.constprop.0+0x594/0x5dc __mutex_lock_slowpath+0x1c/0x30 mutex_lock+0x50/0x60 sec_request_init+0x8c/0x1a0 [hisi_sec2] sec_process+0x28/0x1ac [hisi_sec2] sec_skcipher_crypto+0xf4/0x1d4 [hisi_sec2] sec_skcipher_encrypt+0x1c/0x30 [hisi_sec2] crypto_skcipher_encrypt+0x2c/0x40 crypto_authenc_encrypt+0xc8/0xfc [authenc] crypto_aead_encrypt+0x2c/0x40 echainiv_encrypt+0x144/0x1a0 [echainiv] crypto_aead_encrypt+0x2c/0x40 esp_output_tail+0x348/0x5c0 [esp4] esp_output+0x120/0x19c [esp4] xfrm_output_one+0x25c/0x4d4 xfrm_output_resume+0x6c/0x1fc xfrm_output+0xac/0x3c0 xfrm4_output+0x64/0x130 ip_build_and_send_pkt+0x158/0x20c tcp_v4_send_synack+0xdc/0x1f0 tcp_conn_request+0x7d0/0x994 tcp_v4_conn_request+0x58/0x6c tcp_v6_conn_request+0xf0/0x100 tcp_rcv_state_process+0x1cc/0xd60 tcp_v4_do_rcv+0x10c/0x250 tcp_v4_rcv+0xfc4/0x10a4 ip_protocol_deliver_rcu+0xf4/0x200 ip_local_deliver_finish+0x58/0x70 ip_local_deliver+0x68/0x120 ip_sublist_rcv_finish+0x70/0x94 ip_list_rcv_finish.constprop.0+0x17c/0x1d0 ip_sublist_rcv+0x40/0xb0 ip_list_rcv+0x140/0x1dc __netif_receive_skb_list_core+0x154/0x28c __netif_receive_skb_list+0x120/0x1a0 netif_receive_skb_list_internal+0xe4/0x1f0 napi_complete_done+0x70/0x1f0 gro_cell_poll+0x9c/0xb0 napi_poll+0xcc/0x264 net_rx_action+0xd4/0x21c __do_softirq+0x130/0x358 irq_exit+0x11c/0x13c __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x78/0x2c0 el1_irq+0xb8/0x140 arch_cpu_idle+0x18/0x40 default_idle_call+0x5c/0x1c0 cpuidle_idle_call+0x174/0x1b0 do_idle+0xc8/0x160 cpu_startup_entry+0x30/0x11c secondary_start_kernel+0x158/0x1e4 softirq: huh, entered softirq 3 NET_RX 0000000093774ee4 with preempt_count 00000100, exited with fffffe00?

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel availability bug in the HiSilicon Kunpeng920 SEC encryption driver. Under packet encryption or decryption during softirq processing, the driver can use a mutex where sleeping is not allowed, causing kernel scheduling errors. The sources do not provide CVSS, impact scoring, or evidence of exploitation.

Executive priority

Treat this as targeted platform hygiene, not a broad emergency. Prioritize affected ARM/Kunpeng infrastructure using hardware crypto acceleration, because impact appears availability-oriented and exposure depends on specific hardware and driver use.

Technical view

The affected path is the Linux crypto hisilicon/sec driver, observed through hisi_sec2 during network packet processing such as ESP/XFRM. The issue is a sleep-in-atomic-context defect: sec_request_init uses mutex locking while executing in softirq. Stable kernel commits are referenced as the resolution.

Likely exposure

Exposure is likely limited to Linux systems using the HiSilicon Kunpeng920 SEC crypto driver, especially where kernel crypto offload is used for network packet encryption or decryption. The bundle lists affected Linux kernel versions including 5.5 through fixed stable releases around 5.10.137, 5.15.61, 5.18.18, 5.19.2, and 6.0.

Exploitation context

No active exploitation is stated. The CVE is not marked CISA KEV in the provided bundle. The evidence describes a kernel BUG report triggered during legitimate crypto/network processing, not a weaponized attack chain or remotely proven exploit path.

Researcher notes

The public bundle lacks CVSS, CWE, exploitability analysis, and distro-specific fixed versions. The strongest evidence is the upstream kernel resolution and call trace showing mutex use from softirq context. Avoid expanding scope beyond Linux hisilicon/sec without additional vendor sources.

Mitigation direction

  • Update to a vendor kernel containing the referenced Linux stable fixes.
  • Prioritize hosts using HiSilicon Kunpeng920 SEC or hisi_sec2 crypto acceleration.
  • Check Linux distribution advisories for exact fixed package versions.
  • Do not assume a configuration workaround unless vendor guidance names one.

Validation and detection

  • Inventory Linux hosts using HiSilicon SEC or hisi_sec2 drivers.
  • Compare running kernel versions with vendor fixed package guidance.
  • Review kernel logs for the cited scheduling-while-atomic pattern involving hisi_sec2.
  • Confirm whether IPsec/XFRM or kernel crypto paths use HiSilicon SEC acceleration.
Prepared
Confidence
medium
Sources
7

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-50171 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
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux416d82204df44ef727de6eafafeaa4d12fdc78dc, 416d82204df44ef727de6eafafeaa4d12fdc78dc, 416d82204df44ef727de6eafafeaa4d12fdc78dc, 416d82204df44ef727de6eafafeaa4d12fdc78dc, 416d82204df44ef727de6eafafeaa4d12fdc78dcunaffected
LinuxLinux5.5, 0, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

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