CVE-2026-31587

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

ASoC: qcom: q6apm: move component registration to unmanaged version

q6apm component registers dais dynamically from ASoC toplology, which are allocated using device managed version apis. Allocating both component and dynamic dais using managed version could lead to incorrect free ordering, dai will be freed while component still holding references to it.

Fix this issue by moving component to unmanged version so that the dai pointers are only freeded after the component is removed.

================================================================== BUG: KASAN: slab-use-after-free in snd_soc_del_component_unlocked+0x3d4/0x400 [snd_soc_core] Read of size 8 at addr ffff00084493a6e8 by task kworker/u48:0/3426 Tainted: [W]=WARN Hardware name: LENOVO 21N2ZC5PUS/21N2ZC5PUS, BIOS N42ET57W (1.31 ) 08/08/2024 Workqueue: pdr_notifier_wq pdr_notifier_work [pdr_interface] Call trace: show_stack+0x28/0x7c (C) dump_stack_lvl+0x60/0x80 print_report+0x160/0x4b4 kasan_report+0xac/0xfc __asan_report_load8_noabort+0x20/0x34 snd_soc_del_component_unlocked+0x3d4/0x400 [snd_soc_core] snd_soc_unregister_component_by_driver+0x50/0x88 [snd_soc_core] devm_component_release+0x30/0x5c [snd_soc_core] devres_release_all+0x13c/0x210 device_unbind_cleanup+0x20/0x190 device_release_driver_internal+0x350/0x468 device_release_driver+0x18/0x30 bus_remove_device+0x1a0/0x35c device_del+0x314/0x7f0 device_unregister+0x20/0xbc apr_remove_device+0x5c/0x7c [apr] device_for_each_child+0xd8/0x160 apr_pd_status+0x7c/0xa8 [apr] pdr_notifier_work+0x114/0x240 [pdr_interface] process_one_work+0x500/0xb70 worker_thread+0x630/0xfb0 kthread+0x370/0x6c0 ret_from_fork+0x10/0x20

Allocated by task 77: kasan_save_stack+0x40/0x68 kasan_save_track+0x20/0x40 kasan_save_alloc_info+0x44/0x58 __kasan_kmalloc+0xbc/0xdc __kmalloc_node_track_caller_noprof+0x1f4/0x620 devm_kmalloc+0x7c/0x1c8 snd_soc_register_dai+0x50/0x4f0 [snd_soc_core] soc_tplg_pcm_elems_load+0x55c/0x1eb8 [snd_soc_core] snd_soc_tplg_component_load+0x4f8/0xb60 [snd_soc_core] audioreach_tplg_init+0x124/0x1fc [snd_q6apm] q6apm_audio_probe+0x10/0x1c [snd_q6apm] snd_soc_component_probe+0x5c/0x118 [snd_soc_core] soc_probe_component+0x44c/0xaf0 [snd_soc_core] snd_soc_bind_card+0xad0/0x2370 [snd_soc_core] snd_soc_register_card+0x3b0/0x4c0 [snd_soc_core] devm_snd_soc_register_card+0x50/0xc8 [snd_soc_core] x1e80100_platform_probe+0x208/0x368 [snd_soc_x1e80100] platform_probe+0xc0/0x188 really_probe+0x188/0x804 __driver_probe_device+0x158/0x358 driver_probe_device+0x60/0x190 __device_attach_driver+0x16c/0x2a8 bus_for_each_drv+0x100/0x194 __device_attach+0x174/0x380 device_initial_probe+0x14/0x20 bus_probe_device+0x124/0x154 deferred_probe_work_func+0x140/0x220 process_one_work+0x500/0xb70 worker_thread+0x630/0xfb0 kthread+0x370/0x6c0 ret_from_fork+0x10/0x20

Freed by task 3426: kasan_save_stack+0x40/0x68 kasan_save_track+0x20/0x40 __kasan_save_free_info+0x4c/0x80 __kasan_slab_free+0x78/0xa0 kfree+0x100/0x4a4 devres_release_all+0x144/0x210 device_unbind_cleanup+0x20/0x190 device_release_driver_internal+0x350/0x468 device_release_driver+0x18/0x30 bus_remove_device+0x1a0/0x35c device_del+0x314/0x7f0 device_unregister+0x20/0xbc apr_remove_device+0x5c/0x7c [apr] device_for_each_child+0xd8/0x160 apr_pd_status+0x7c/0xa8 [apr] pdr_notifier_work+0x114/0x240 [pdr_interface] process_one_work+0x500/0xb70 worker_thread+0x630/0xfb0 kthread+0x370/0x6c0 ret_from_fork+0x10/0x20

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (7)

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

ASoC: qcom: q6apm: move component registration to unmanaged version - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: qcom: q6apm: move component registration to unmanaged version - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: qcom: q6apm: move component registration to unmanaged version - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: qcom: q6apm: move component registration to unmanaged version - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/887632163b546a8944b46ef465f1d74e838b727a
generic

ASoC: qcom: q6apm: move component registration to unmanaged version - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ec1235fc941dac6c011b30ee01d9220ff87e0cd
generic

ASoC: qcom: q6apm: move component registration to unmanaged version - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30383b7780ffa140bc124de5b66cae7c84133dbb
generic

ASoC: qcom: q6apm: move component registration to unmanaged version - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/110769a9aa51135ac7ce479a47dfb41924f37664

Vendor Advisories for CVE-2026-31587(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.175—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
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 (126 versions)6.19.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(18)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 69× 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 255 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31587?
CVE-2026-31587 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: q6apm: move component registration to unmanaged version q6apm component registers dais dynamically from ASoC toplology, which are allocated using device managed version apis. Allocating both component and dynamic dais…
When was CVE-2026-31587 disclosed?
CVE-2026-31587 was first published in the National Vulnerability Database on April 24, 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-2026-31587 actively exploited?
CVE-2026-31587 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 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-31587?
CVE-2026-31587 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31587?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31587, 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-2026-31587

Explore →

Is Your Infrastructure Affected by CVE-2026-31587?

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

Start Free Scan →Browse All CVEs