Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2022-50426 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

remoteproc: imx_dsp_rproc: Add mutex protection for workqueue

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

remoteproc: imx_dsp_rproc: Add mutex protection for workqueue

The workqueue may execute late even after remoteproc is stopped or

stopping, some resources (rpmsg device and endpoint) have been

released in rproc_stop_subdevices(), then rproc_vq_interrupt()

accessing these resources will cause kennel dump.

Call trace:

virtqueue_add_split+0x1ac/0x560

virtqueue_add_inbuf+0x4c/0x60

rpmsg_recv_done+0x15c/0x294

vring_interrupt+0x6c/0xa4

rproc_vq_interrupt+0x30/0x50

imx_dsp_rproc_vq_work+0x24/0x40 [imx_dsp_rproc]

process_one_work+0x1d0/0x354

worker_thread+0x13c/0x470

kthread+0x154/0x160

ret_from_fork+0x10/0x20

Add mutex protection in imx_dsp_rproc_vq_work(), if the state is

not running, then just skip calling rproc_vq_interrupt().

Also the flush workqueue operation can't be added in rproc stop

for the same reason. The call sequence is

rproc_shutdown

-> rproc_stop

->rproc_stop_subdevices

->rproc->ops->stop()

->imx_dsp_rproc_stop

->flush_work

-> rproc_vq_interrupt

The resource needed by rproc_vq_interrupt has been released in

rproc_stop_subdevices, so flush_work is not safe to be called in

imx_dsp_rproc_stop.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2022-50426 is recorded against 2 packages.

  • kernel (from 6.1.0 up to 6.1.4)
  • linux-kernel (from 6.1 up to 6.1.4)

Timeline and source

Published on 1 October 2025 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2022-50426 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-10-01
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.1.0 6.1.4
linux-kernel 6.1 6.1.4

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2022-50426 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2022
✓