CVE-2026-31602: ALSA: ctxfi: Limit PTP to a single page
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.
Security readout for executives and security teams
Plain-English summary
A low-privileged local user may be able to crash an affected Linux system through audio operations using the ALSA ctxfi driver. The driver can access memory beyond its allocated page-table space. The published score asserts confidentiality, integrity, and availability impact, although the supplied technical evidence specifically demonstrates a kernel page fault.
Executive priority
Treat this as a prompt patching priority for workstations or specialist systems using ctxfi audio hardware. Priority can be reduced after confirming the driver path is absent. It is not presented as an internet-wide emergency because exploitation requires local access and no active exploitation is documented.
Technical view
A prior change increased CT_PTP_NUM from one to four, but ct_vm_map() continued using only vm->ptp[0]. On AMD64, that page covers 512 entries, or 2 MiB. Larger aggregate allocations cause an out-of-bounds access and kernel page fault. The stable fix restores CT_PTP_NUM to one.
Likely exposure
Exposure is concentrated on systems running an affected Linux kernel with the ctxfi audio driver and compatible hardware present or usable. Systems without that driver path are unlikely to be exposed. The supplied version data does not provide clear branch boundaries, so verify distribution backports using the cited fix commits.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. This CVE is not listed as KEV, and the supplied sources report neither active exploitation nor a public proof of concept. The documented result is a kernel page fault during PCM playback preparation.
Researcher notes
The supplied affected-version data is internally difficult to interpret, including repeated commit identifiers and mixed release values. Validate each distribution kernel through backport records rather than version strings alone. The trace demonstrates an out-of-bounds kernel access and page fault; broader confidentiality and integrity consequences are asserted by CVSS but not demonstrated in the description.
Mitigation direction
Update affected systems to vendor-supported kernels containing the applicable cited stable fix.
Prioritize updates where the ctxfi driver and associated audio hardware are present or usable.
If updating is delayed, consult distribution guidance; the supplied sources name no separate workaround.
Validation and detection
Inventory running kernel versions and determine whether snd_ctxfi is loaded or bound to hardware.
Check kernel changelogs or source for the applicable cited stable fix commit.
After updating, verify the fixed kernel is running, not merely installed.
Monitor kernel logs for ct_vm_map page faults during normal audio operations.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31602 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
10Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.