scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 55f4b1f73631a0817717fe6e98517de51b4c3527 · < 5b9f1ef293428ea9c0871d96fcec2a87c4445832| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE
On Google gs101, the number of UTP transfer request slots (nutrs) is 32, and in this case the driver ends up programming the UTRL_NEXUS_TYPE incorrectly as 0.
This is because the left hand side of the shift is 1, which is of type int, i.e. 31 bits wide. Shifting by more than that width results in undefined behaviour.
Fix this by switching to the BIT() macro, which applies correct type casting as required. This ensures the correct value is written to UTRL_NEXUS_TYPE (0xffffffff on gs101), and it also fixes a UBSAN shift warning:
UBSAN: shift-out-of-bounds in drivers/ufs/host/ufs-exynos.c:1113:21 shift exponent 32 is too large for 32-bit type 'int'
For consistency, apply the same change to the nutmrs / UTMRL_NEXUS_TYPE write.
From the CVE record · Linux
On Google gs101 systems with 32 UTP transfer request slots, the Linux kernel Exynos UFS driver can program UTRL_NEXUS_TYPE as zero because of an undefined shift. The input does not describe what an attacker could do or specify network access, authentication requirements, or user interaction.
Engineers running the Linux kernel on Google gs101 systems should check their Exynos UFS driver; affected versions are not specified.