dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 26 Feb 2025.
Debian LinuxOperating system · Debian

CVE-2024-53104

HIGH · 7.8 CVSS v3.1 Published 2024-12-02
Fix available
A fix is available. Upgrade to 4.19.324 / 5.4.286 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild 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: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format This can lead to out of bounds writes since frames of this type were not taken into account when calculating the size of the frames buffer in uvc_parse_streaming.

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 · high confidence

The Linux kernel's UVC video driver (uvcvideo) has an out-of-bounds write vulnerability. When parsing video format descriptors, frames of type UVC_VS_UNDEFINED were being parsed in uvc_parse_format but were not accounted for in the buffer size calculation in uvc_parse_streaming, leading to buffer overflows.

MitigationApply the kernel patch to skip parsing undefined frame types in uvc_parse_format, or update to a kernel version containing this fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Debian LinuxOperating system
Affected:= 11.0
Linux KernelOperating system
Affected:>= 2.6.26, < 4.19.324>= 4.20, < 5.4.286>= 5.5, < 5.10.230>= 5.11, < 5.15.172>= 5.16, < 6.1.117>= 6.2, < 6.6.61>= 6.7, < 6.11.8>= 6.12, < 6.12.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
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify kernel version
    Run `uname -r` or check `/proc/version` to get the running kernel version
    Affected if The kernel version falls within any of these ranges: < 4.19.324, >= 4.20 and < 5.4.286, >= 5.5 and < 5.10.230, >= 5.11 and < 5.15.172, >= 5.16 and < 6.1.117, >= 6.2 and < 6.6.61, >= 6.7 and < 6.11.8, or >= 6.12 and < 6.12.1
  2. Check if uvcvideo module is present
    Run `lsmod | grep uvcvideo` or check for the presence of `/sys/module/uvcvideo`
    Affected if The uvcvideo kernel module is loaded or loadable on the system
  3. Verify USB video device enumeration
    Run `lsusb` or check `/sys/class/video4linux` to see if any USB video devices are present
    Affected if A USB video device (webcam) is plugged in and recognized by the system, which triggers the UVC driver to parse format descriptors

The system is affected if it runs a vulnerable kernel version AND has the uvcvideo driver available AND has a USB video device connected that triggers the vulnerable parsing code path.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.19.324 / 5.4.286 / 5.10.230 or later
Fixed in 4.19.3245.4.2865.10.230
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch to skip parsing undefined frame types in uvc_parse_format, or update to a kernel version containing this fix.

Recommended fix High confidence

Linux Kernel 4.19.324 / 5.4.286 / 5.10.230 / 5.15.172 or later (or any stable kernel >= 6.1)

  1. 1. Identify the currently running kernel version using 'uname -r'
  2. 2. Check if the current kernel version is affected (version < 4.19.324, < 5.4.286, < 5.10.230, or < 5.15.172)
  3. 3. For Debian 11 systems: Run 'apt update' followed by 'apt upgrade linux-image-*' to install the fixed kernel package
  4. 4. For other systems: Install a kernel package from a fixed release (4.19.324+, 5.4.286+, 5.10.230+, or 5.15.172+)
  5. 5. Reboot the system to load the fixed kernel
  6. 6. Verify the running kernel is now a fixed version using 'uname -r'
Caveat Kernel upgrades may require rebooting and could introduce compatibility issues with out-of-tree drivers or custom modules; ensure critical hardware drivers are available in the new kernel

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

Fix this in Debian Linux Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53104 — 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-2024-53104 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