Security readout for executives and security teams
Plain-English summary
This is a Linux kernel denial-of-service issue in the s5p_cec media driver. A local low-privileged user may be able to trigger an oversized CEC message length handling case, causing availability impact. It is not described as data theft or privilege escalation in the provided sources.
Executive priority
Handle through normal kernel patch management, with higher priority for systems where local users can access affected media hardware paths. This is availability-focused and local, not a cited remote compromise issue.
Technical view
The fix bounds msg.len to CEC_MAX_MSG_SIZE in the Linux s5p_cec driver. The CVSS vector is local, low complexity, low privileges, no user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact.
Likely exposure
Exposure is likely limited to Linux systems running affected kernels with the s5p_cec media driver present and reachable locally. Internet-facing exposure is not indicated by the CVSS vector or sources.
Exploitation context
The source bundle marks KEV as false and provides no evidence of active exploitation. The CVSS vector indicates local authenticated access is required. Public exploit status is not established in the provided evidence.
Researcher notes
Evidence is sparse: the kernel note states the hardware likely limits length to 16 but adds a defensive CEC_MAX_MSG_SIZE check. Validate downstream backports carefully because version lists and commit hashes vary across stable branches.
Mitigation direction
- Update affected Linux kernels using vendor or distribution packages containing the stable fixes.
- Prioritize systems where the s5p_cec driver is enabled or relevant hardware is present.
- If no vendor package is available, track Linux stable commits and distribution advisories.
- Consider disabling unused s5p_cec driver exposure where operationally safe and vendor-supported.
Validation and detection
- Inventory Linux kernel versions against vendor advisories for CVE-2022-49035.
- Check whether the s5p_cec driver is built, loaded, or used on relevant systems.
- Confirm deployed kernels include the referenced stable commits or downstream backports.
- Review local-access systems for unusual availability events if the driver is present.
Public sources used
- CVE Program
- CVE List V5
- Linux stable commit 7ccb40f26cbefa1c6dfd3418bea54c9518cdbd8a
- Linux stable commit fc0f76dd5f116fa9291327024dda392f8b4e849c
- Linux stable commit a2728bf9b6c65e46468c763e3dab7e04839d4e11
- Linux stable commit 4a449430ecfb199b99ba58af63c467eb53500b39
- Linux stable commit 1609231f86760c1f6a429de7913dd795b9faa08c
- Linux stable commit cbfa26936f318b16ccf9ca31b8e8b30c0dc087bd
- Linux stable commit 2654e785bd4aa2439cdffbe7dc1ea30a0eddbfe4
- Linux stable commit 93f65ce036863893c164ca410938e0968964b26c
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-770: 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-2022-49035 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
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
1 official scoreWe 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:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
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/7ccb40f26cbefa1c6dfd3418bea54c9518cdbd8aCVE reference, Linux
- https://git.kernel.org/stable/c/fc0f76dd5f116fa9291327024dda392f8b4e849cCVE reference, Linux
- https://git.kernel.org/stable/c/a2728bf9b6c65e46468c763e3dab7e04839d4e11CVE reference, Linux
- https://git.kernel.org/stable/c/4a449430ecfb199b99ba58af63c467eb53500b39CVE reference, Linux
- https://git.kernel.org/stable/c/1609231f86760c1f6a429de7913dd795b9faa08cCVE reference, Linux
- https://git.kernel.org/stable/c/cbfa26936f318b16ccf9ca31b8e8b30c0dc087bdCVE reference, Linux
- https://git.kernel.org/stable/c/2654e785bd4aa2439cdffbe7dc1ea30a0eddbfe4CVE reference, Linux
- https://git.kernel.org/stable/c/93f65ce036863893c164ca410938e0968964b26cCVE 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.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.