Bug 2516527 (CVE-2026-72261)

Summary: CVE-2026-72261 kernel: ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's Sound Open Firmware (SOF) subsystem, specifically within the `ipc3-control` component. This vulnerability occurs in the `snd_sof_update_control()` function where the size of firmware-provided data is not properly validated against the allocated buffer size. An attacker could exploit this by providing a malformed size, leading to a buffer overflow. This could result in memory corruption, potentially causing system instability or a denial of service.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-15 06:17:10 UTC 
In the Linux kernel, the following vulnerability has been resolved:

ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control

In snd_sof_update_control(), firmware-provided cdata->num_elems is
checked against local_cdata->data->size but never against the actual
allocation size. If local_cdata->data->size was previously set to an
inconsistent value, the memcpy could write past the allocated buffer.

Add a bounds check to ensure num_elems fits within the available space
in the ipc_control_data allocation before copying.
Comment 1 Keith Grant 2026-08-18 18:10:56 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026081555-CVE-2026-72261-b28a@gregkh/T
Comment 7 Jon Orris 2026-09-23 18:08:45 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:71016 https://access.redhat.com/errata/RHSA-2026:71016
Comment 8 Jon Orris 2026-09-24 01:02:43 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:71213 https://access.redhat.com/errata/RHSA-2026:71213
Comment 9 Jon Orris 2026-09-24 05:52:44 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:71232 https://access.redhat.com/errata/RHSA-2026:71232