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 30 Apr 2025.
Linux KernelOperating system · Linux

CVE-2024-53197

HIGH · 7.8 CVSS v3.1 Published 2024-12-27
Fix available
A fix is available. Upgrade to 4.19.325 / 5.4.287 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: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices A bogus device can provide a bNumConfigurations value that exceeds the initial value used in usb_get_configuration for allocating dev->config. This can lead to out-of-bounds accesses later, e.g. in usb_destroy_configuration.

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 USB audio driver (ALSA) has an out-of-bounds access vulnerability where a malicious or faulty USB device can report a bNumConfigurations value larger than the initially allocated buffer (dev->config). Since no bounds validation occurs before allocation, subsequent accesses to dev->config in functions like usb_destroy_configuration can read/write beyond the allocated array bounds.

MitigationApply the kernel patch that adds bounds validation for bNumConfigurations before the configuration array is allocated; users should avoid connecting untrusted USB devices until kernel is updated.

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
Linux KernelOperating system
Affected:>= 2.6.12, < 4.19.325>= 4.20, < 5.4.287>= 5.5, < 5.10.231>= 5.11, < 5.15.174>= 5.16, < 6.1.120>= 6.2, < 6.6.64>= 6.7, < 6.11.11>= 6.12, < 6.12.2
Debian LinuxOperating system
Affected:= 11.0

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 the running Linux kernel version
    Run 'uname -r' to obtain the exact kernel version string
    Affected if the version falls within any of the affected ranges: < 4.19.325, >= 4.20 and < 5.4.287, >= 5.5 and < 5.10.231, >= 5.11 and < 5.15.174, >= 5.16 and < 6.1.120, >= 6.2 and < 6.6.64, >= 6.7 and < 6.11.11, or >= 6.12 and < 6.12.2
  2. Check if the snd-usb-audio kernel module is loaded
    Run 'lsmod | grep snd-usb-audio' or inspect /proc/asound/modules
    Affected if the snd-usb-audio module is currently loaded in memory
  3. Identify connected USB audio devices
    Run 'lsusb' to list all USB devices and check for Creative Labs Extigy (041e:3000) or Mbox (041e:3010/3011) device IDs, or run 'cat /proc/asound/cards' to list detected ALSA sound cards
    Affected if an Extigy or Mbox USB audio device is connected to the system
  4. Verify Debian version if applicable
    Run 'cat /etc/debian_version' to confirm the Debian release
    Affected if the system is Debian 11.0

A system is affected if it runs a vulnerable kernel version AND has the snd-usb-audio driver available AND has an Extigy or Mbox USB audio device connected, allowing a malicious USB device to trigger the buffer overflow via bNumConfigurations.

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.325 / 5.4.287 / 5.10.231 or later
Fixed in 4.19.3255.4.2875.10.231
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch that adds bounds validation for bNumConfigurations before the configuration array is allocated; users should avoid connecting untrusted USB devices until kernel is updated.

Recommended fix High confidence

Linux Kernel 6.6 or later (or minimum fixed version per branch: 4.19.325, 5.4.287, 5.10.231, 5.15.174)

  1. 1. Identify the current kernel version by running: uname -r
  2. 2. For Debian 11 (Bullseye), update the package lists: apt-get update
  3. 3. Upgrade the kernel package: apt-get install linux-image-<version> (or apt-get dist-upgrade for full upgrade)
  4. 4. Reboot the system to load the new kernel: reboot
  5. 5. After reboot, verify the new kernel version is running: uname -r
  6. 6. Ensure the version is >= 4.19.325, >= 5.4.287, >= 5.10.231, or >= 5.15.174 (or >= 6.6 for latest stable)
Caveat Kernel upgrades may require rebooting and could introduce compatibility issues with custom kernel modules or specific hardware drivers; test in staging environment first

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

Fix this in Linux Kernel Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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