linux-cve-announce - CVE-2025-21873: scsi: ufs: core: bsg: Fix crash when arpmb command fails

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: <2025032709-CVE-2025-21873-311e@gregkh>
Date: Thu, 27 Mar 2025 15:58:07 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-21873: scsi: ufs: core: bsg: Fix crash when arpmb command fails

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

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

scsi: ufs: core: bsg: Fix crash when arpmb command fails

If the device doesn't support arpmb we'll crash due to copying user data in
bsg_transport_sg_io_fn().

In the case where ufs_bsg_exec_advanced_rpmb_req() returns an error, do not
set the job's reply_len.

Memory crash backtrace:
3,1290,531166405,-;ufshcd 0000:00:12.5: ARPMB OP failed: error code -22

4,1308,531166555,-;Call Trace:

4,1309,531166559,-; <TASK>

4,1310,531166565,-; ? show_regs+0x6d/0x80

4,1311,531166575,-; ? die+0x37/0xa0

4,1312,531166583,-; ? do_trap+0xd4/0xf0

4,1313,531166593,-; ? do_error_trap+0x71/0xb0

4,1314,531166601,-; ? usercopy_abort+0x6c/0x80

4,1315,531166610,-; ? exc_invalid_op+0x52/0x80

4,1316,531166622,-; ? usercopy_abort+0x6c/0x80

4,1317,531166630,-; ? asm_exc_invalid_op+0x1b/0x20

4,1318,531166643,-; ? usercopy_abort+0x6c/0x80

4,1319,531166652,-; __check_heap_object+0xe3/0x120

4,1320,531166661,-; check_heap_object+0x185/0x1d0

4,1321,531166670,-; __check_object_size.part.0+0x72/0x150

4,1322,531166679,-; __check_object_size+0x23/0x30

4,1323,531166688,-; bsg_transport_sg_io_fn+0x314/0x3b0

The Linux kernel CVE team has assigned CVE-2025-21873 to this issue.


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

	Issue introduced in 6.3 with commit 6ff265fc5ef660499e0edc4641647e99eed3f519 and fixed in 6.6.81 with commit 32fb5ec825f6f76bc28902181c65429a904a07fe
	Issue introduced in 6.3 with commit 6ff265fc5ef660499e0edc4641647e99eed3f519 and fixed in 6.12.18 with commit 59455f968c1004ed897ba873237657745d81ce0f
	Issue introduced in 6.3 with commit 6ff265fc5ef660499e0edc4641647e99eed3f519 and fixed in 6.13.6 with commit 7e3c96ff5c5f3206984ed077b2aa8c9b7c4e0327
	Issue introduced in 6.3 with commit 6ff265fc5ef660499e0edc4641647e99eed3f519 and fixed in 6.14 with commit f27a95845b01e86d67c8b014b4f41bd3327daa63

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-2025-21873
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/ufs/core/ufs_bsg.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/32fb5ec825f6f76bc28902181c65429a904a07fe
	https://git.kernel.org/stable/c/59455f968c1004ed897ba873237657745d81ce0f
	https://git.kernel.org/stable/c/7e3c96ff5c5f3206984ed077b2aa8c9b7c4e0327
	https://git.kernel.org/stable/c/f27a95845b01e86d67c8b014b4f41bd3327daa63