CVE-2022-49617 | ASoC: Intel: sof_sdw: handle errors on card registration

In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: sof_sdw: handle errors on card registration If the card registration fails, typically because of deferred probes, the device properties added for headset codecs are not removed, which leads to kernel oopses in driver bind/unbind tests. We already clean-up the device properties when the card is removed, this code can be moved as a helper and called upon card registration errors.

Published: 2025-02-26 Last update: 2025-10-23 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-49617 is rated Low Risk (29.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.07%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-49617

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-06 0.03% 0.07% +0.04%
2 2026-01-09 0.05% 0.03% -0.02%
3 2025-11-22 — 0.05% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49617

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2022-49617

OS Trackers for CVE-2022-49617

vendor priority summary link
debian not yet assigned CVE-2022-49617 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2022-49617
redhat medium — https://access.redhat.com/security/cve/CVE-2022-49617
suse medium — https://www.suse.com/security/cve/CVE-2022-49617/
ubuntu medium CVE-2022-49617 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 150, released 114, not-affected 99, needed 42, needs-triage 1. https://ubuntu.com/security/CVE-2022-49617

Affected software / configurations for CVE-2022-49617

Vendor Product Version Raw CPE
linux linux_kernel >= 5.7, < 5.15.56 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 5.18.13 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 5.19 cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:*
linux linux_kernel 5.19 cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:*
linux linux_kernel 5.19 cpe:2.3:o:linux:linux_kernel:5.19:rc3:*:*:*:*:*:*
linux linux_kernel 5.19 cpe:2.3:o:linux:linux_kernel:5.19:rc4:*:*:*:*:*:*
linux linux_kernel 5.19 cpe:2.3:o:linux:linux_kernel:5.19:rc5:*:*:*:*:*:*

References for CVE-2022-49617

cvelogic Threat Intelligence