linux-cve-announce - CVE-2022-50421: rpmsg: char: Avoid double destroy of default endpoint

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025100155-CVE-2022-50421-8bdc@gregkh>
Date: Wed,  1 Oct 2025 13:41:54 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50421: rpmsg: char: Avoid double destroy of default endpoint

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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

rpmsg: char: Avoid double destroy of default endpoint

The rpmsg_dev_remove() in rpmsg_core is the place for releasing
this default endpoint.

So need to avoid destroying the default endpoint in
rpmsg_chrdev_eptdev_destroy(), this should be the same as
rpmsg_eptdev_release(). Otherwise there will be double destroy
issue that ept->refcount report warning:

refcount_t: underflow; use-after-free.

Call trace:
 refcount_warn_saturate+0xf8/0x150
 virtio_rpmsg_destroy_ept+0xd4/0xec
 rpmsg_dev_remove+0x60/0x70

The issue can be reproduced by stopping remoteproc before
closing the /dev/rpmsgX.

The Linux kernel CVE team has assigned CVE-2022-50421 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.18 with commit bea9b79c2d10fecf7bfa26e212ecefe61d232e39 and fixed in 5.19.17 with commit ef828a39d6a7028836eaf37df3ad568c8c2dd6f9
	Issue introduced in 5.18 with commit bea9b79c2d10fecf7bfa26e212ecefe61d232e39 and fixed in 6.0.3 with commit 3f20ef7a845c2c8d7ec82ecffa20d95cab5ecfeb
	Issue introduced in 5.18 with commit bea9b79c2d10fecf7bfa26e212ecefe61d232e39 and fixed in 6.1 with commit 467233a4ac29b215d492843d067a9f091e6bf0c5

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-50421
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/rpmsg/rpmsg_char.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/ef828a39d6a7028836eaf37df3ad568c8c2dd6f9
	https://git.kernel.org/stable/c/3f20ef7a845c2c8d7ec82ecffa20d95cab5ecfeb
	https://git.kernel.org/stable/c/467233a4ac29b215d492843d067a9f091e6bf0c5