CVE-2024-38621: media: stk1160: fix bounds checking in stk1160_copy_video()
In the Linux kernel, the following vulnerability has been resolved:
media: stk1160: fix bounds checking in stk1160copyvideo()
The subtract in this condition is reversed. The ->length is the length of the buffer. The ->bytesused is how many bytes we have copied thus far. When the condition is reversed that means the result of the subtraction is always negative but since it's unsigned then the result is a very high positive value. That means the overflow check is never true.
Additionally, the ->bytesused doesn't actually work for this purpose because we're not writing to "buf->mem + buf->bytesused". Instead, the math to calculate the destination where we are writing is a bit involved. You calculate the number of full lines already written, multiply by two, skip a line if necessary so that we start on an odd numbered line, and add the offset into the line.
To fix this buffer overflow, just take the actual destination where we are writing, if the offset is already out of bounds print an error and return. Otherwise, write up to buf->length bytes.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-38621?
CVE-2024-38621 is considered a medium severity vulnerability due to potential buffer overrun risks in the Linux kernel.
How do I fix CVE-2024-38621?
To fix CVE-2024-38621, update your Linux kernel to version 5.10.223-1, 5.10.226-1, 6.1.119-1, 6.1.123-1, 6.12.11-1, or 6.12.12-1.
Which software is affected by CVE-2024-38621?
CVE-2024-38621 affects specific versions of the Linux kernel, particularly those mentioned in the recent updates.
What is the nature of CVE-2024-38621?
CVE-2024-38621 involves an issue with bounds checking in the stk1160 video driver function in the Linux kernel.
Is CVE-2024-38621 actively exploited?
As of now, there is no evidence to suggest that CVE-2024-38621 is actively being exploited in the wild.