CVE-2024-53104

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Linux Kernel. For every flaw being used in attacks, see Exploited flaws; for Linux’s, see Linux flaws being used in attacks.

CVE-2024-53104 is a security flaw in Linux Kernel, the core of Linux, which runs most servers, Android phones and many home routers. Someone who already has a foothold can use Linux Kernel to take full control of the machine. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 5 Feb 2025.[1]

Linux Kernel is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Fixed by 8 commits to Linux, in the releases that include them.

Description

CISA calls it an out-of-bounds write in Linux Kernel. In its words: “Linux kernel contains an out-of-bounds write vulnerability in the uvc_parse_streaming component of the USB Video Class (UVC) driver that could allow for physical escalation of privilege.”[1]

The CVE record adds: “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.”[2]

The underlying weakness is out-of-bounds write (CWE-787), in MITRE’s list of common software weaknesses.

It scores 7.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]

ProductFixed in
Linuxcommit 95edf13a48e7
Linuxcommit 684022f81f12
Linuxcommit faff5bbb2762
Linuxcommit 467d84dc78c9
Linuxcommit beced2cb09b5
Linuxcommit 575a562f7a3e
Linuxcommit 622ad10aae5f
Linuxcommit 1ee9d9122801

Most families won’t have Linux Kernel; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 5 Feb 2025, 65 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 26 Feb 2025 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 3%. That’s in the top 12% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Linux has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.”[1]

  1. Check whether you use it.Linux Kernel is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed (fixed by 8 commits to Linux, in the releases that include them), or not in use. CISA gave US government agencies until 26 Feb 2025 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 7.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 3%.[4]

See also

Other Linux Kernel flaws

Other out-of-bounds write flaws

  • CVE-2026-86950, Apple devices: out-of-bounds write ·
  • CVE-2026-87491, Chrome and other Chromium browsers: out of bounds write ·
  • CVE-2026-11645, Chrome and other Chromium browsers: out-of-bounds read and write ·
  • CVE-2026-0300, Palo Alto Networks PAN-OS: out-of-bounds write ·
  • CVE-2026-3909, Google Skia: out-of-bounds write ·

Every Linux flaw on CISA’s list · Everything added in February 2025

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Linux Kernel Out-of-Bounds Write Vulnerability”. Known Exploited Vulnerabilities Catalog, added 5 Feb 2025.
  2. ^ National Institute of Standards and Technology. “CVE-2024-53104 Detail”. National Vulnerability Database, published 2 Dec 2024.
  3. ^ Linux. Advisories and fixes: lore.kernel.org, git.kernel.org, git.kernel.org, git.kernel.org, git.kernel.org, and 3 more on NVD’s record.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.034, percentile 88.8, 31 Oct 2026.
  5. CVE Program. “CVE-2024-53104”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.