tee: optee: Fix supplicant wait loop
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 · < fd9d2d6124c293e40797a080adf8a9c237efd8b8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tee: optee: Fix supplicant wait loop
OP-TEE supplicant is a user-space daemon and it's possible for it be hung or crashed or killed in the middle of processing an OP-TEE RPC call. It becomes more complicated when there is incorrect shutdown ordering of the supplicant process vs the OP-TEE client application which can eventually lead to system hang-up waiting for the closure of the client application.
Allow the client process waiting in kernel for supplicant response to be killed rather than indefinitely waiting in an unkillable state. Also, a normal uninterruptible wait should not have resulted in the hung-task watchdog getting triggered, but the endless loop would.
This fixes issues observed during system reboot/shutdown when supplicant got hung for some reason or gets crashed/killed which lead to client getting hung in an unkillable state. It in turn lead to system being in hung up state requiring hard power off/on to recover.
From the CVE record · Linux
The Linux kernel's OP-TEE supplicant wait loop can leave a client process stuck in an unkillable state if the user-space supplicant hangs, crashes, or is killed during an RPC call. Incorrect shutdown ordering can then leave the system hung, including during reboot or shutdown; the input does not describe an attacker or exploitation conditions.
Engineers running Linux systems that use OP-TEE should check their kernel versions; affected versions are not specified.