Linux vulnerability

In the Linux kernel, the following vulnerability has been resolved: greybus: audio: bound the topology section sizes against the fetched size gb_audio_gb_get_topology() fetches a topology blob of a module-supplied size, and gbaudio_tplg_parse_data() then walks it by adding the module-supplied size_dais, size_controls and size_widgets fields to form the control, widget and route section offsets. Those le32 sizes are never checked against the fetched blob, so a module reporting a small topology size but large section sizes makes the offsets point past the allocation, and parsing reads out of bounds. Reject a topology whose section sizes do not fit within the fetched size before it is parsed.

Published 24 Sep 2026Updated 25 Sep 20268 sources
CVSS 8.8

What happened

In the Linux kernel, the following vulnerability has been resolved: greybus: audio: bound the topology section sizes against the fetched size gb_audio_gb_get_topology() fetches a topology blob of a module-supplied size, and gbaudio_tplg_parse_data() then walks it by adding the module-supplied size_dais, size_controls and size_widgets fields to form the control, widget and route section offsets. Those le32 sizes are never checked against the fetched blob, so a module reporting a small topology size but large section sizes makes the offsets point past the allocation, and parsing reads out of bounds. Reject a topology whose section sizes do not fit within the fetched size before it is parsed.

Affected versions

Linux: 184992e305f1de3a3d5fa446da3a2bc76be7c54a through before ba86de9f7b0d7903d2df5ea2373e34d8ca3fc43e (git); 184992e305f1de3a3d5fa446da3a2bc76be7c54a through before dd5593aee0a0fb353e1164aff7b65e563fe1f232 (git); 184992e305f1de3a3d5fa446da3a2bc76be7c54a through before 6f764363b3173d805be11e59a8f23ecee2d420d5 (git); 184992e305f1de3a3d5fa446da3a2bc76be7c54a through before 52daf9de692ebac813d110eb1e677dc0e1f4a5ab (git); 184992e305f1de3a3d5fa446da3a2bc76be7c54a through before d0f6eaba60705bacd9bb4ce48eab50ef3f546777 (git); 184992e305f1de3a3d5fa446da3a2bc76be7c54a through before c9191f2e2f35f1209eb2dc24b31129dd47b48c16 (git); 184992e305f1de3a3d5fa446da3a2bc76be7c54a through before cfcc5a41a9664eb68023aae4cd0d485b256bd7c7 (git); 184992e305f1de3a3d5fa446da3a2bc76be7c54a through before 33d8c7b794d2a30637c9d3fcb478f1d3222bef1e (git); 4.9 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.