CVE-2024-49981

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

media: venus: fix use after free bug in venus_remove due to race condition

in venus_probe, core->work is bound with venus_sys_error_handler, which is used to handle error. The code use core->sys_err_done to make sync work. The core->work is started in venus_event_notify.

If we call venus_remove, there might be an unfished work. The possible sequence is as follows:

CPU0 CPU1

                 |venus_sys_error_handler

venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev

Fix it by canceling the work in venus_remove.

Weakness

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Software

Extended Description

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:

A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Potential Mitigations

• Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
• Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/26.html
• https://cwe.mitre.org/data/definitions/29.html

References

• https://git.kernel.org/stable/c/10941d4f99a5a34999121b314afcd9c0a1c14f15
• https://git.kernel.org/stable/c/2a541fcc0bd2b05a458e9613376df1289ec11621
• https://git.kernel.org/stable/c/5098b9e6377577fe13d03e1d8914930f014a3314
• https://git.kernel.org/stable/c/60b6968341a6dd5353554f3e72db554693a128a5
• https://git.kernel.org/stable/c/63bbe26471ebdcc3c20bb4cc3950d666279ad658
• https://git.kernel.org/stable/c/b0686aedc5f1343442d044bd64eeac7e7a391f4e
• https://git.kernel.org/stable/c/bf6be32e2d39f6301ff1831e249d32a8744ab28a
• https://git.kernel.org/stable/c/c5a85ed88e043474161bbfe54002c89c1cb50ee2
• https://git.kernel.org/stable/c/d925e9f7fb5a2dbefd1a73fc01061f38c7becd4c
• https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
• https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html