LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46049: ALSA: ctxfi: Add fallback to default RSR for S/PDIF

In the Linux kernel, the following vulnerability has been resolved: ALSA: ctxfi: Add fallback to default RSR for S/PDIF spdif_passthru_playback_get_resources() uses atc->pll_rate as the RSR for the MSR calculation loop. However, pll_rate is only updated in atc_pll_init() and not in hw_pll_init(), so it remains 0 after the card init. When spdif_passthru_playback_setup() skips atc_pll_init() for 32000 Hz, (rsr * desc.msr) always becomes 0, causing the loop to spin indefinitely. Add fallback to use atc->rsr when atc->pll_rate is 0. This reflects the hardware state, since hw_card_init() already configures the PLL to the default RSR.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can make the affected Creative X-Fi ALSA audio driver spin indefinitely during specific S/PDIF passthrough handling. Business impact is most likely local availability disruption on systems using this hardware and driver path. The source bundle provides no CVSS score and no evidence of active exploitation.

Executive priority

Treat as targeted availability risk, not a broad internet-facing emergency based on current evidence. Prioritize normal kernel patching, with faster handling for workstations or appliances that use affected audio hardware.

Technical view

The ctxfi driver uses atc->pll_rate as the reference sample rate in spdif_passthru_playback_get_resources(). When pll_rate remains zero after card initialization and 32000 Hz setup skips atc_pll_init(), the MSR calculation loop can spin indefinitely. The fix falls back to atc->rsr when pll_rate is zero.

Likely exposure

Exposure appears limited to Linux systems with affected kernel builds using the ALSA ctxfi driver and relevant S/PDIF passthrough behavior. The provided data does not identify remote exposure, affected distributions, or default exploitability.

Exploitation context

No active exploitation is supported by the provided sources, and KEV is false. The source describes an indefinite loop caused by driver state during S/PDIF setup, but does not state required privileges, attack path, or real-world abuse.

Researcher notes

The vulnerable condition is tied to pll_rate remaining zero and 32000 Hz S/PDIF passthrough setup avoiding atc_pll_init(). Evidence supports a kernel driver infinite loop fix, but not severity scoring, exploit prerequisites, or distribution-specific status.

Mitigation direction

  • Apply the relevant Linux stable kernel update containing the ctxfi fallback fix.
  • Confirm whether your distribution has backported one of the referenced stable commits.
  • Prioritize systems with Creative X-Fi or ctxfi audio hardware and S/PDIF use.
  • If updates are unavailable, check vendor guidance for supported temporary mitigations.

Validation and detection

  • Inventory kernels and identify systems loading the ALSA ctxfi driver.
  • Compare installed kernel packages against distribution advisories and fixed stable commits.
  • Review audio hardware inventory for Creative X-Fi or compatible ctxfi devices.
  • Confirm no operational dependence on vulnerable S/PDIF passthrough paths remains unpatched.
Prepared
Confidence
medium
Sources
10

Public sources used

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-46049 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8cc72361481f00253f1e468ade5795427386d593, 8cc72361481f00253f1e468ade5795427386d593, 8cc72361481f00253f1e468ade5795427386d593, 8cc72361481f00253f1e468ade5795427386d593, 8cc72361481f00253f1e468ade5795427386d593, 8cc72361481f00253f1e468ade5795427386d593, 8cc72361481f00253f1e468ade5795427386d593, 8cc72361481f00253f1e468ade5795427386d593unaffected
LinuxLinux2.6.31, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.