CVE-2026-31602

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:

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)
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 (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.

Patch Availability(1)

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
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—

Additional Vendor Advisories

(24)

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

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 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-31602 actively exploited?
CVE-2026-31602 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.0% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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