Menu

Star on GitHub · 3.2k

CVE-2026-74499

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: fix OOB write in snd_usbmidi_akai_output() snd_usbmidi_akai_output() computes its fill-loop bound buf_end =…

Published Aug 15, 2026EPSS 0.18%

Overview

CVE-2026-74499 is a known-severity vulnerability. It was published on August 15, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

ALSA: usb-audio: fix OOB write in snd_usbmidi_akai_output()

snd_usbmidi_akai_output() computes its fill-loop bound

buf_end = ep->max_transfer - MAX_AKAI_SYSEX_LEN - 1;

as a signed int, so a small device-advertised bulk-OUT max_transfer

makes buf_end negative. The loop guard then compares the u32

urb->transfer_buffer_length against that negative int: the usual

arithmetic conversion turns buf_end into a large unsigned value, so the

guard stays true and each iteration keeps appending SysEx framing and

payload bytes past the end of the URB transfer buffer, which is only

max_transfer bytes long.

A USB device that advertises a tiny bulk-OUT endpoint can therefore

trigger an attacker-length- and content-controlled heap out-of-bounds

write when a process writes to the created /dev/snd/midiC*D* node.

Return early when there is no room for even one SysEx, so the loop is

never entered with a bound that would wrap. The lo

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-74499?

CVE-2026-74499 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-74499?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-74499?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-74499?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-74499 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.