dbcve.org
Linux KernelOperating system · Linux

CVE-2022-49035

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-02
Fix available
A fix is available. Upgrade to 4.9.333 / 4.14.299 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE I expect that the hardware will have limited this to 16, but just in case it hasn't, check for this corner case.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-770

The application allocates memory, connections, or handles in response to a request without enforcing any cap, so a modest amount of malicious traffic exhausts the resource and denies service to everyone else. The fix is enforcing quotas, limits, and timeouts on what any single request or client can consume.

General guidance for the resource allocation without limits class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:< 4.9.333>= 4.10, < 4.14.299>= 4.15, < 4.19.265>= 4.20, < 5.4.224>= 5.5, < 5.10.154>= 5.11, < 5.15.78>= 5.16, < 6.0.8= 6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.9.333 / 4.14.299 / 4.19.265 or later
Fixed in 4.9.3334.14.2994.19.265
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 4.9.333 / 4.14.299 / 4.19.265 / 5.4.224 or later (depending on your branch)

  1. Identify your current Linux kernel version using 'uname -r'
  2. Determine which kernel branch you are on (4.9.x, 4.14.x, 4.19.x, or 5.4.x)
  3. For kernel 4.9.x: upgrade to version 4.9.333 or later
  4. For kernel 4.14.x: upgrade to version 4.14.299 or later
  5. For kernel 4.19.x: upgrade to version 4.19.265 or later
  6. For kernel 5.4.x: upgrade to version 5.4.224 or later
  7. Alternatively, apply the upstream commit 1609231f86760c1f6a429de7913dd795b9faa08c which adds 'msg.len = min(msg.len, CEC_MAX_MSG_SIZE);' to enforce the 16-byte CEC message limit
  8. Reboot into the updated kernel
Caveat Kernel upgrades may introduce compatibility changes with proprietary drivers or specific hardware configurations; test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-49035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-49035 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data