Skip to content
vulnerability

CVE-2024-53104

7.8
High
KEV · Exploited in wildEPSS 3%Patch available

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.

exploited
Yes, in CISA KEV since 5 Feb 2025fix by 26 Feb 2025 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Fixed in < 2.6.26, >= 4.19.324 and <= 4.19.*, >= 5.4.286 and <= 5.4.* +7
likelihood
EPSS 3.4%
Published 2 Dec 2024Analysed here 2 Nov 2026CVSS scored by CISA

do firstUpgrade to a fixed release: < 2.6.26, >= 4.19.324 and <= 4.19.*, >= 5.4.286 and <= 5.4.*, >= 5.10.230 and <= 5.10.* (+6 more below).

triage
server-sideruntimeWAF can block: noAV · localCWE-787· Out-of-Bounds Write

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2024-53104 being exploited?

Yes. CVE-2024-53104 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-53104?

CVE-2024-53104 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-53104?

Yes. A fix has been recorded for CVE-2024-53104. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-53104 affect?

CVE-2024-53104 affects debian:debian_linux, linux:linux_kernel. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
debian:debian_linuxlinux:linux_kernel
affected versions
Linux
  • affected>= c0efd232929c2cd87238de2cccdaf4e845be5b0c and < 95edf13a48e75dc2cc5b0bc57bf90d6948a22fe8
  • affected>= c0efd232929c2cd87238de2cccdaf4e845be5b0c and < 684022f81f128338fe3587ec967459669a1204ae
  • affected>= c0efd232929c2cd87238de2cccdaf4e845be5b0c and < faff5bbb2762c44ec7426037b3000e77a11d6773
  • affected>= c0efd232929c2cd87238de2cccdaf4e845be5b0c and < 467d84dc78c9abf6b217ada22b3fdba336262e29
  • affected>= c0efd232929c2cd87238de2cccdaf4e845be5b0c and < beced2cb09b58c1243733f374c560a55382003d6
  • affected>= c0efd232929c2cd87238de2cccdaf4e845be5b0c and < 575a562f7a3ec2d54ff77ab6810e3fbceef2a91d
  • affected>= c0efd232929c2cd87238de2cccdaf4e845be5b0c and < 622ad10aae5f5e03b7927ea95f7f32812f692bb5
  • affected>= c0efd232929c2cd87238de2cccdaf4e845be5b0c and < 1ee9d9122801eb688783acd07791f2906b87cb4f
  • affected>= c0efd232929c2cd87238de2cccdaf4e845be5b0c and < ecf2b43018da9579842c774b7f35dbe11b5c38dd
  • affected2.6.26
vendor says fixed in< 2.6.26, >= 4.19.324 and <= 4.19.*, >= 5.4.286 and <= 5.4.*, >= 5.10.230 and <= 5.10.*, >= 5.15.172 and <= 5.15.*, >= 6.1.117 and <= 6.1.*, >= 6.6.61 and <= 6.6.*, >= 6.11.8 and <= 6.11.*, >= 6.12.1 and <= 6.12.*, >= 6.13 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 21 Apr 2025 (SSVC 2.0.3).

timeline

  1. 2 Dec 2024Published
  2. 5 Feb 2025Added to CISA KEV (exploited in the wild) · 65 days (about 2 months) later
  3. 26 Feb 2025CISA remediation due date (US federal agencies) · 21 days later
  4. 21 Apr 2025CISA SSVC assessment: exploitation active · 55 days later
  5. 11 May 2026CVE record last updated · 385 days (about 1 year) later
  6. 17 Jul 2026First proof-of-concept repository on GitHub (unvetted) · 66 days (about 2 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 109 days (about 4 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
12 references in the CVE record: 12 links
Show 4 more
  • Linkgit.kernel.org /stable/c/ecf2b43018da9579842c774b7f35dbe11b5c38dd
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-53104
  • Linklists.debian.org /debian-lts-announce/2025/03/msg00002.html
  • Linklists.debian.org /debian-lts-announce/2025/01/msg00001.html

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved