CVE-2025-71286

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-06. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls

The size of the data behind of scontrol->ipc_control_data for bytes controls is: [1] sizeof(struct sof_ipc4_control_data) + // kernel only struct [2] sizeof(struct sof_abi_hdr)) + payload

The max_size specifies the size of [2] and it is coming from topology.

Change the function to take this into account and allocate adequate amount of memory behind scontrol->ipc_control_data.

With the change we will allocate [1] amount more memory to be able to hold the full size of data.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a704a1a4394b5877b9adc31b2c3165ad0b541896
generic

ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a653820700b81c9e6f05ac23b7969ecec1a18e85
generic

ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59fe643f21b9d59bcbedb0dfbf988ee455c23736
generic

ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/491956b45b5f4933632ea6d8a8bdfdf045ab81e1
generic

ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1237cd9ff198cb882402572f29569e5247190974

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
linuxKernel @ 6.6.128—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1—

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 225 total refreshes for this CVE.

  1. 2026-09-15 03:10 UTCEPSS rescore
  2. 2026-09-13 16:46 UTCEPSS rescore
  3. 2026-09-12 15:00 UTCEPSS rescore
  4. 2026-09-11 16:23 UTCOSV refresh
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:00 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-08-30 01:21 UTCEPSS rescore
  15. 2026-08-28 21:40 UTCEPSS rescore
  16. 2026-08-27 14:24 UTCEPSS rescore
  17. 2026-08-26 14:45 UTCEPSS rescore
  18. 2026-08-25 13:48 UTCEPSS rescore
  19. 2026-08-24 14:16 UTCEPSS rescore
  20. 2026-08-23 20:18 UTCEG score recompute
  21. 2026-08-23 20:18 UTCVendor advisory
  22. 2026-08-23 20:18 UTCGHSA enrichment
  23. 2026-08-23 00:18 UTCEPSS rescore
  24. 2026-08-21 23:48 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:46 UTCEPSS rescore
  4. 2026-08-17 12:59 UTCEG score recompute
  5. 2026-08-17 12:59 UTCVendor advisory
  6. 2026-08-17 12:59 UTCGHSA enrichment
  7. 2026-08-16 14:55 UTCEPSS rescore
  8. 2026-08-16 04:55 UTCEG score recompute
  9. 2026-08-16 04:55 UTCVendor advisory
  10. 2026-08-16 04:55 UTCGHSA enrichment
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 02:30 UTCEG score recompute
  13. 2026-08-15 02:30 UTCVendor advisory
  14. 2026-08-15 02:30 UTCGHSA enrichment
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 03:30 UTCEG score recompute
  17. 2026-08-14 03:30 UTCVendor advisory
  18. 2026-08-14 03:30 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-12 17:02 UTCEG score recompute
  21. 2026-08-12 17:02 UTCVendor advisory
  22. 2026-08-12 17:02 UTCGHSA enrichment
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-11 13:42 UTCEPSS rescore
  25. 2026-08-11 08:31 UTCEG score recompute
  26. 2026-08-11 08:31 UTCVendor advisory
  27. 2026-08-11 08:31 UTCGHSA enrichment
  28. 2026-08-10 23:59 UTCEPSS rescore
  29. 2026-08-10 09:30 UTCEG score recompute
  30. 2026-08-10 09:30 UTCVendor advisory
  31. 2026-08-10 09:30 UTCGHSA enrichment
  32. 2026-08-09 13:46 UTCEPSS rescore
  33. 2026-08-09 10:30 UTCEG score recompute
  34. 2026-08-09 10:30 UTCVendor advisory
  35. 2026-08-09 10:30 UTCGHSA enrichment
  36. 2026-08-08 16:36 UTCEPSS rescore
  37. 2026-08-08 10:15 UTCEG score recompute
  38. 2026-08-08 10:15 UTCVendor advisory
  39. 2026-08-08 10:15 UTCGHSA enrichment
  40. 2026-08-07 16:27 UTCEPSS rescore
  41. 2026-08-07 11:15 UTCEG score recompute
  42. 2026-08-07 11:15 UTCVendor advisory
  43. 2026-08-07 11:14 UTCGHSA enrichment
  44. 2026-08-06 13:46 UTCEPSS rescore
  45. 2026-08-06 11:46 UTCEG score recompute
  46. 2026-08-06 11:46 UTCVendor advisory
  47. 2026-08-06 11:46 UTCGHSA enrichment
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-05 12:33 UTCEG score recompute
  50. 2026-08-05 12:33 UTCVendor advisory
  51. 2026-08-05 12:33 UTCGHSA enrichment
  52. 2026-08-04 10:37 UTCEPSS rescore
  53. 2026-08-04 03:42 UTCEG score recompute
  54. 2026-08-04 03:42 UTCVendor advisory
  55. 2026-08-04 03:42 UTCGHSA enrichment
  56. 2026-08-03 10:35 UTCEPSS rescore
  57. 2026-08-03 04:41 UTCVendor advisory
  58. 2026-08-03 04:41 UTCGHSA enrichment
  59. 2026-08-02 05:10 UTCEG score recompute
  60. 2026-08-02 05:10 UTCVendor advisory
  61. 2026-08-02 05:10 UTCGHSA enrichment
  62. 2026-08-02 02:26 UTCEPSS rescore
  63. 2026-08-01 04:15 UTCEPSS rescore
  64. 2026-07-30 16:27 UTCEPSS rescore
  65. 2026-07-30 06:41 UTCEG score recompute
  66. 2026-07-30 06:41 UTCVendor advisory
  67. 2026-07-30 06:41 UTCGHSA enrichment
  68. 2026-07-30 01:30 UTCEPSS rescore
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-25 14:17 UTCEPSS rescore
  72. 2026-07-25 14:17 UTCEPSS rescore
  73. 2026-07-24 14:17 UTCEPSS rescore
  74. 2026-07-23 03:03 UTCEG score recompute
  75. 2026-07-22 14:08 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-71286?
CVE-2025-71286 is a medium vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls The size of the data behind of scontrol->ipccontroldata for bytes controls is: [1] sizeof(struct sofipc4control_data) + // kernel only struct [2]…
When was CVE-2025-71286 disclosed?
CVE-2025-71286 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71286 actively exploited?
CVE-2025-71286 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.5% of all scored CVEs.
What is the CVSS score of CVE-2025-71286?
CVE-2025-71286 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-71286?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71286, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71286

Explore →

Is Your Infrastructure Affected by CVE-2025-71286?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs