Answer in brief
CVE-2024-38621 records a Unknown severity vulnerability in media: stk1160: fix bounds checking in stk1160_copy_video(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9cb2173e6ea8f2948bd1367c93083a2500fcf08f <f6a392266276730bea893b55d12940e32a25f56a || >=9cb2173e6ea8f2948bd1367c93083a2500fcf08f <ecf4ddc3aee8ade504c4d36b7b4053ce6093e200 || >=9cb2173e6ea8f2948bd1367c93083a2500fcf08f <a16775828aaed1c54ff4e6fe83e8e4d5c6a50cb7 || >=9cb2173e6ea8f2948bd1367c93083a2500fcf08f <7532bcec0797adfa08791301c3bcae14141db3bd || >=9cb2173e6ea8f2948bd1367c93083a2500fcf08f <b504518a397059e1d55c521ba0ea2b545a6c4b52 || >=9cb2173e6ea8f2948bd1367c93083a2500fcf08f <d410017a7181cb55e4a5c810b32b75e4416c6808 || >=9cb2173e6ea8f2948bd1367c93083a2500fcf08f <a08492832cc4cacc24e0612f483c86ca899b9261 || >=9cb2173e6ea8f2948bd1367c93083a2500fcf08f <faa4364bef2ec0060de381ff028d1d836600a381 | f6a392266276730bea893b55d12940e32a25f56a, ecf4ddc3aee8ade504c4d36b7b4053ce6093e200, a16775828aaed1c54ff4e6fe83e8e4d5c6a50cb7, 7532bcec0797adfa08791301c3bcae14141db3bd, b504518a397059e1d55c521ba0ea2b545a6c4b52, d410017a7181cb55e4a5c810b32b75e4416c6808, a08492832cc4cacc24e0612f483c86ca899b9261, faa4364bef2ec0060de381ff028d1d836600a381 |
| Linux/Linuxgeneric | 3.7 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
Published upstream
Jun 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.