CVE-2026-31602

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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:

ALSA: ctxfi: Limit PTP to a single page

Commit 391e69143d0a increased CT_PTP_NUM from 1 to 4 to support 256 playback streams, but the additional pages are not used by the card correctly. The CT20K2 hardware already has multiple VMEM_PTPAL registers, but using them separately would require refactoring the entire virtual memory allocation logic.

ct_vm_map() always uses PTEs in vm->ptp[0].area regardless of CT_PTP_NUM. On AMD64 systems, a single PTP covers 512 PTEs (2M). When aggregate memory allocations exceed this limit, ct_vm_map() tries to access beyond the allocated space and causes a page fault:

BUG: unable to handle page fault for address: ffffd4ae8a10a000 Oops: Oops: 0002 [#1] SMP PTI RIP: 0010:ct_vm_map+0x17c/0x280 [snd_ctxfi] Call Trace: atc_pcm_playback_prepare+0x225/0x3b0 ct_pcm_playback_prepare+0x38/0x60 snd_pcm_do_prepare+0x2f/0x50 snd_pcm_action_single+0x36/0x90 snd_pcm_action_nonatomic+0xbf/0xd0 snd_pcm_ioctl+0x28/0x40 __x64_sys_ioctl+0x97/0xe0 do_syscall_64+0x81/0x610 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Revert CT_PTP_NUM to 1. The 256 SRC_RESOURCE_NUM and playback_count remain unchanged.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
3.1%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

Advisory Details (6)

Auto-updated Apr 29, 2026
No patch confirmed yet.
generic

ALSA: ctxfi: Limit PTP to a single page - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: ctxfi: Limit PTP to a single page - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: ctxfi: Limit PTP to a single page - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: ctxfi: Limit PTP to a single page - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/452894005b4abe141b11fe01e7bfe152e6d3860f
generic

ALSA: ctxfi: Limit PTP to a single page - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3fd0685d7fef68c2d8a04876bcf9eaa0724ad6a5
generic

ALSA: ctxfi: Limit PTP to a single page - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/365c36e1a126c6aa1aecedd3a351bcabc66f0c29

Vendor Advisories for CVE-2026-31602(2)

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

Data Freshness Timeline

(refreshed 6× 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 162 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-31602?
CVE-2026-31602 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: ctxfi: Limit PTP to a single page Commit 391e69143d0a increased CTPTPNUM from 1 to 4 to support 256 playback streams, but the additional pages are not used by the card correctly. The CT20K2 hardware already has multiple…
When was CVE-2026-31602 disclosed?
CVE-2026-31602 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31602 actively exploited?
CVE-2026-31602 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31602?
CVE-2026-31602 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31602?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31602, 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

Explore the affected products and dependency analysis for CVE-2026-31602

Explore →

Is Your Infrastructure Affected by CVE-2026-31602?

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

Start Free Scan →Browse All CVEs