Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in dfc00979ff00d9dfdfa1df32144a272ee2728102 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in dfc00979ff00d9dfdfa1df32144a272ee2728102, d0b53842211f73a10ea174100a213f7fa14b9f33, 09496158f6ebba8830593f8972035c02f97124c1 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < dfc00979ff00d9dfdfa1df32144a272ee2728102
Fixed in
  • dfc00979ff00d9dfdfa1df32144a272ee2728102
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < d0b53842211f73a10ea174100a213f7fa14b9f33
Fixed in
  • d0b53842211f73a10ea174100a213f7fa14b9f33
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < 09496158f6ebba8830593f8972035c02f97124c1
Fixed in
  • 09496158f6ebba8830593f8972035c02f97124c1
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < 615b7a5e5d8be68d52f262579906f7e015ba4606
Fixed in
  • 615b7a5e5d8be68d52f262579906f7e015ba4606
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < 95b1ee8442cabbde83b2848e7c6100df90f3a00d
Fixed in
  • 95b1ee8442cabbde83b2848e7c6100df90f3a00d
LinuxLinuxAffected
  • ≥ 8cc72361481f00253f1e468ade5795427386d593, < 30f9494c6f2b53a78822cfb653ffbb1d092d44c8
Fixed in
  • 30f9494c6f2b53a78822cfb653ffbb1d092d44c8

Description

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.

References

Community reviews

Loading reviews…