Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s vivid media driver can write beyond an internal array when more than 32 video-capture buffers are used. The documented result is a kernel crash; the CVSS assessment also reflects possible confidentiality, integrity, and availability impact. Exploitation requires local, low-privileged access.
Executive priority
Prioritize affected multi-user, development, testing, or media-processing systems where local users can access vivid functionality. Treat internet-only exposure as unlikely from the supplied evidence. Remediate through normal high-severity kernel patching, accelerating systems with untrusted local users or accessible media devices.
Technical view
The capture queue allowed up to 64 buffers, while the must_blank array retained a 32-entry limit. Buffer indices 32 or higher therefore caused a CWE-787 out-of-bounds write. The referenced kernel changes introduce a consistent MAX_VID_CAP_BUFFERS limit for the array and queue.
Likely exposure
Exposure requires an affected Linux build, the vulnerable vivid capture path, and a local user able to request more than 32 buffers. The supplied version data references 6.8, 6.11.8, and 6.12 but is insufficiently clear to define a reliable range; confirm against vendor advisories and fix commits.
Exploitation context
The CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, and no user interaction. The supplied sources document an out-of-bounds write and reported crash. This CVE is not listed as KEV, and the bundle provides no evidence of active exploitation or public weaponization.
Researcher notes
The source establishes an index-bound mismatch: a 64-buffer queue accessed a 32-entry array. A crash is confirmed, but stronger impact such as privilege escalation is not demonstrated in the bundle. Review both stable commits and downstream backports because version metadata alone is ambiguous. Avoid treating CVSS impact assumptions as proof of practical exploitation.
Mitigation direction
- Update to a vendor-supported Linux kernel that incorporates the referenced stable fixes.
- Check distribution or appliance vendor guidance for exact corrected package versions.
- Restrict local access to systems where the vulnerable vivid media path is available.
- If operationally acceptable, disable unnecessary vivid functionality until the corrected kernel is deployed.
Validation and detection
- Inventory kernel builds on systems where vivid media functionality may be available.
- Confirm corrected packages contain one of the referenced stable fixes or an equivalent backport.
- Verify whether the vivid driver and affected video-capture queue are enabled or accessible.
- After updating, confirm systems boot normally and report the intended corrected kernel build.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-50288 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/e6bacd8f2178b22859fe6d9f755f19dfcd9d3862CVE reference, Linux
- https://git.kernel.org/stable/c/96d8569563916fe2f8fe17317e20e43f54f9ba4bCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.