media: venus: Fix OOB read due to missing payload bound check
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 09c2845e8fe4fcab942929480203f504a6e0a114 · < 06d6770ff0d8cc8dfd392329a8cc03e2a83e7289| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
media: venus: Fix OOB read due to missing payload bound check
Currently, The event_seq_changed() handler processes a variable number of properties sent by the firmware. The number of properties is indicated by the firmware and used to iterate over the payload. However, the payload size is not being validated against the actual message length.
This can lead to out-of-bounds memory access if the firmware provides a property count that exceeds the data available in the payload. Such a condition can result in kernel crashes or potential information leaks if memory beyond the buffer is accessed.
Fix this by properly validating the remaining size of the payload before each property access and updating bounds accordingly as properties are parsed.
This ensures that property parsing is safely bounded within the received message buffer and protects against malformed or malicious firmware behavior.
From the CVE record · Linux
The Linux kernel's Venus event handler does not check that a firmware-supplied property count fits within the message payload. Malformed or malicious firmware data can cause an out-of-bounds read, potentially crashing the kernel or leaking information; the input does not specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with the Venus media component should check their systems; affected versions are not specified.