[CVE-2024-53104][MODERATE 7.0] media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format

[CVE-2024-53104][MODERATE 7.0] media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format

[AL-KERNEL]

CVE: CVE-2024-53104
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format
Commit: 95edf13a48e75dc2cc5b0bc57bf90d6948a22fe8
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=95edf13a48e75dc2cc5b0bc57bf90d6948a22fe8
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2024-53104
Analysis date: Wed, 16 Sep 2026 13:09:51 -0400
ActionableScore: 5
ActionableScore lower bound: unknown
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2024-53104 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2024-53104

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2024-53104	MODERATE	https://www.kernelcve.org/list/?q=CVE-2024-53104 CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H';*CWE-787;CWE-131;*CWE-20;BEST CVSS score: '6.8';DESCR 'An out of bounds write in the uvcvideo parser can occur when uvc_parse_format() parses frame descriptors of type UVC_VS_UNDEFINED that were not counted when sizing the frames buffer. A crafted USB Video Class device can expose such descriptors during enumeration and cause kernel memory corruption while the host parses the device descriptors. For the CVSS the PR:N value is used because no host privileges are required once the attacker can present the malicious USB device to the system. The issue is not network reachable in the normal model and is best treated as a physical USB attack vector. Impact is at least denial of service via kernel crash and may include confidentiality and integrity impact because the bug class is an out of bounds write in kernel memory.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5) 	MAYBE	WRITE OOB USB SIMPLEFIX HARDWARE LINUS KPANIC  KPANIC DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN6	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=5
PrimitiveClass=CLASS_A
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=NO
ImportantCandidate=YES
ManualReview=REQUIRED
AutoDowngradeAllowed=NO

1. ActionableScore

* Raw conservative score: 4
* Conservative score: 5
* Raw paranoid score: 4
* Paranoid score: 5
* Applied conservative floor/cap: strong kernel OOB write manual-review floor 4 -> 5
* Applied paranoid floor/cap: strong kernel OOB write manual-review floor 4 -> 5
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

2. Signal breakdown

Positive signals:

* +2: Strong corruption primitive. The commit explicitly states that parsing UVC_VS_UNDEFINED frame descriptors can lead to out of bounds writes because these frames were not counted when sizing the frames buffer.
* +1: Firmware/device-mediated external influence. A crafted USB Video Class device can supply malicious descriptors that reach the vulnerable parser during enumeration.
* +1: Reliable kernel crash / strong DoS. Kernel heap corruption from an OOB write can realistically crash the host kernel.
* +1: Broad/common parser exposure. uvcvideo is a common USB camera driver and descriptor parsing is exercised automatically when a matching device is enumerated.
* +1: Memory layout invariant mismatch. The allocation/counting logic in uvc_parse_streaming and the parsing loop in uvc_parse_format disagreed about which frame descriptor types could be written into the frames buffer.

Negative signals:

* -2: Physical-only attack vector. The supplied evidence supports a malicious local USB device scenario, not network reachability.

Important non-awarded signals:

* RealUAF is not awarded because this is an OOB write, not a lifetime bug.
* Controlled reclaim is not demonstrated.
* Arbitrary kernel read/write is not demonstrated.
* Direct network reachability is not established.
* Extra availability is not awarded because the crash/DoS consequence is already counted once.
* C/I are not separately awarded as ActionableScore points merely because an OOB write could theoretically corrupt sensitive objects. The stronger fact is captured as Class A kernel corruption.

3. Reachability analysis

The realistic attacker is a person or device able to present a crafted USB Video Class device to the target system. No host administrator privilege is required once the attacker can connect or emulate the malicious USB device. The vulnerable operation occurs during device descriptor parsing by the kernel driver, so the attacker does not need a local shell or a privileged process on the host.

This is not namespace-scoped. User namespaces and network namespaces are not relevant. There is no evidence of a remote network trigger. Prior privileged setup is not required in the usual case if the kernel has uvcvideo support and automatically binds the device. The main prerequisite is physical or equivalent USB-device presentation capability.

Race repeatability is not relevant because this is a deterministic parser/allocation mismatch rather than a timing race.

4. Primitive and severity interpretation

The exact primitive is an attacker-influenced kernel out of bounds write during UVC descriptor parsing. The bug is caused by parsing frame descriptors of type UVC_VS_UNDEFINED even though those descriptors were not included in the frame-buffer sizing calculation.

This is active kernel heap corruption, not a fixed stale buffer and not a cleanup-only stale dereference. No concrete repeated release/refcount operation exists. The first demonstrated consequence is likely kernel crash or memory corruption during USB device enumeration. A stronger consequence such as privilege escalation is plausible enough to require review because the primitive is an OOB write in kernel memory, but controlled target selection, controlled reclaim, arbitrary write, or a complete LPE chain is not established by the supplied evidence.

PrimitiveClass is CLASS_A because an attacker-influenced OOB write is directly established. ImportantCandidate is YES because Class A corruption should not be automatically downgraded even though the attack vector is physical. AutoDowngradeAllowed is NO because automatic closure would discard a concrete kernel memory corruption primitive.

Likely operational severity is actionable Moderate with Strong Important review potential. The physical USB requirement prevents treating it as a high-end remote issue, but the kernel OOB write prevents treating it as ordinary Low or routine DoS.

5. One-sentence report phrase

A crafted USB Video Class device can trigger an out of bounds write in uvcvideo descriptor parsing by using UVC_VS_UNDEFINED frame descriptors that were not counted in the frames buffer size, causing kernel memory corruption and at least a host DoS with possible stronger impact requiring manual review.

6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch establishes a real attacker-influenced kernel OOB write, and although the vector is physical USB rather than network, the corruption primitive is strong enough that automatic downgrade is unsafe.

7. Call-site confidence

Call-site confidence: medium

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format
Commit: 95edf13a48e75dc2cc5b0bc57bf90d6948a22fe8
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=95edf13a48e75dc2cc5b0bc57bf90d6948a22fe8

Commit description:

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.

Fixes: c0efd23 ("V4L/DVB (8145a): USB Video Class driver")
Signed-off-by: Benoit Sevens <bsevens@google.com>
Cc: stable@vger.kernel.org
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/media/usb/uvc/uvc_driver.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=95edf13a48e75dc2cc5b0bc57bf90d6948a22fe8

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2024-53104 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2024-53104

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: Not available
  The Best / paranoid CVSS vector: AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 6.8

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 5

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).