linux-cve-announce - CVE-2022-50382: padata: Always leave BHs disabled when running ->parallel()

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: <2025091851-CVE-2022-50382-0ff0@gregkh>
Date: Thu, 18 Sep 2025 15:33:56 +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-50382: padata: Always leave BHs disabled when running ->parallel()

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

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

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

padata: Always leave BHs disabled when running ->parallel()

A deadlock can happen when an overloaded system runs ->parallel() in the
context of the current task:

    padata_do_parallel
      ->parallel()
        pcrypt_aead_enc/dec
          padata_do_serial
            spin_lock(&reorder->lock) // BHs still enabled
              <interrupt>
                ...
                  __do_softirq
                    ...
                      padata_do_serial
                        spin_lock(&reorder->lock)

It's a bug for BHs to be on in _do_serial as Steffen points out, so
ensure they're off in the "current task" case like they are in
padata_parallel_worker to avoid this situation.

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


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

	Issue introduced in 5.8 with commit 4611ce22468895acd61fee9ac1da810d60617d9a and fixed in 5.10.163 with commit 8e0681dd4eee029eb1d533d06993f7cb091efb73
	Issue introduced in 5.8 with commit 4611ce22468895acd61fee9ac1da810d60617d9a and fixed in 5.15.86 with commit 17afa98bccec4f52203508b3f49b5f948c6fd6ac
	Issue introduced in 5.8 with commit 4611ce22468895acd61fee9ac1da810d60617d9a and fixed in 6.0.16 with commit 7337adb20fcc0aebb50eaff2bc5a8dd9a7c6743d
	Issue introduced in 5.8 with commit 4611ce22468895acd61fee9ac1da810d60617d9a and fixed in 6.1.2 with commit 6cfa9e60c0f88fdec6368e081ab968411cc706b1
	Issue introduced in 5.8 with commit 4611ce22468895acd61fee9ac1da810d60617d9a and fixed in 6.2 with commit 34c3a47d20ae55b3600fed733bf96eafe9c500d5

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-50382
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:
	kernel/padata.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/8e0681dd4eee029eb1d533d06993f7cb091efb73
	https://git.kernel.org/stable/c/17afa98bccec4f52203508b3f49b5f948c6fd6ac
	https://git.kernel.org/stable/c/7337adb20fcc0aebb50eaff2bc5a8dd9a7c6743d
	https://git.kernel.org/stable/c/6cfa9e60c0f88fdec6368e081ab968411cc706b1
	https://git.kernel.org/stable/c/34c3a47d20ae55b3600fed733bf96eafe9c500d5