Home/CVE/In the Linux kernel, the following vulnerability has been resolved:
ASoC: codecs: wcd938x: fix incorrect used of portid
CVE
CVE-2022-48716
In the Linux kernel, the following vulnerability has been resolved:
ASoC: codecs: wcd938x: fix incorrect used of portid
In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd938x: fix incorrect used of portid Mixer controls have the channel id in mixer-reg, which is not same as port id. port id should be derived from chan_info array. So fix this. Without this, its possible that we could corrupt struct wcd938x_sdw_priv by accessing port_map array out of range with channel id instead of port id.
CRITICAL · CVSS 9.8
EPSS 0.00106
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2022-48716, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
3Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
▤
Affected Products & Versions
3▤
Affected Packages
40Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Ubuntu:20.04:LTS
linux
fixed in 5.4.0-9.12
Ubuntu:20.04:LTS
linux-aws
fixed in 5.4.0-1005.5
Ubuntu:20.04:LTS
linux-aws-5.11
Ubuntu:20.04:LTS
linux-aws-5.13
Ubuntu:20.04:LTS
linux-aws-5.15
fixed in 5.15.0-1014.18~20.04.1
Ubuntu:20.04:LTS
linux-aws-5.8
Ubuntu:20.04:LTS
linux-azure
fixed in 5.4.0-1006.6
Ubuntu:20.04:LTS
linux-azure-5.11
Ubuntu:20.04:LTS
linux-azure-5.13
Ubuntu:20.04:LTS
linux-azure-5.15
fixed in 5.15.0-1007.8~20.04.1
Ubuntu:20.04:LTS
linux-azure-5.8
Ubuntu:20.04:LTS
linux-azure-fde
Ubuntu:20.04:LTS
linux-azure-fde-5.15
fixed in 5.15.0-1019.24~20.04.1.1
Ubuntu:20.04:LTS
linux-bluefield
fixed in 5.4.0-1007.10
Ubuntu:20.04:LTS
linux-gcp
fixed in 5.4.0-1005.5
Ubuntu:20.04:LTS
linux-gcp-5.11
Ubuntu:20.04:LTS
linux-gcp-5.13
Ubuntu:20.04:LTS
linux-gcp-5.15
fixed in 5.15.0-1006.9~20.04.1
Ubuntu:20.04:LTS
linux-gcp-5.8
Ubuntu:20.04:LTS
linux-gke
Ubuntu:20.04:LTS
linux-gke-5.15
Ubuntu:20.04:LTS
linux-gkeop
fixed in 5.4.0-1008.9
Ubuntu:20.04:LTS
linux-gkeop-5.15
fixed in 5.15.0-1003.5~20.04.2
Ubuntu:20.04:LTS
linux-hwe-5.11
Ubuntu:20.04:LTS
linux-hwe-5.13
Ubuntu:20.04:LTS
linux-hwe-5.15
fixed in 5.15.0-33.34~20.04.1
Ubuntu:20.04:LTS
linux-hwe-5.8
Ubuntu:20.04:LTS
linux-ibm
fixed in 5.4.0-1003.4
Ubuntu:20.04:LTS
linux-ibm-5.15
fixed in 5.15.0-1033.36~20.04.1
Ubuntu:20.04:LTS
linux-intel-5.13
Ubuntu:20.04:LTS
linux-intel-iotg-5.15
fixed in 5.15.0-1008.11~20.04.1
Ubuntu:20.04:LTS
linux-iot
fixed in 5.4.0-1001.3
Ubuntu:20.04:LTS
linux-kvm
fixed in 5.4.0-1004.4
Ubuntu:20.04:LTS
linux-lowlatency-hwe-5.15
fixed in 5.15.0-33.34~20.04.1
Ubuntu:20.04:LTS
linux-oem-5.10
Ubuntu:20.04:LTS
linux-oem-5.13
Ubuntu:20.04:LTS
linux-oem-5.14
Ubuntu:20.04:LTS
linux-oem-5.6
Ubuntu:20.04:LTS
linux-oracle
fixed in 5.4.0-1005.5
Ubuntu:20.04:LTS
linux-oracle-5.11
📦
Fixed versions by distribution
31The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15cluster-md-kmp-rt fixed in 0:5.14.21-150500.13.61.1
suse sle15dlm-kmp-rt fixed in 0:5.14.21-150500.13.61.1
suse sle15gfs2-kmp-rt fixed in 0:5.14.21-150500.13.61.1
suse sle15kernel-64kb fixed in 0:5.14.21-150500.55.73.1
suse sle15kernel-azure fixed in 0:5.14.21-150500.33.60.1
suse sle15kernel-default fixed in 0:5.14.21-150500.55.73.1
suse sle15kernel-default-base open
suse sle15kernel-default-devel open
suse sle15kernel-default-extra fixed in 0:5.14.21-150500.55.73.1
suse sle15kernel-default-livepatch fixed in 0:5.14.21-150500.55.73.1
suse sle15kernel-default-livepatch-devel open
suse sle15kernel-default-man open
suse sle15kernel-devel open
suse sle15kernel-docs fixed in 0:5.14.21-150500.55.73.2
suse sle15kernel-livepatch-5_14_21-150500_13_61-rt fixed in 0:1-150500.11.3.1
suse sle15kernel-livepatch-5_14_21-150500_55_73-default fixed in 0:1-150500.11.3.1
suse sle15kernel-macros open
suse sle15kernel-obs-build fixed in 0:5.14.21-150500.55.73.1
suse sle15kernel-rt fixed in 0:5.14.21-150500.13.61.1
suse sle15kernel-rt-vdso fixed in 0:5.14.21-150500.13.61.1
suse sle15kernel-rt_debug fixed in 0:5.14.21-150500.13.61.1
suse sle15kernel-rt_debug-vdso fixed in 0:5.14.21-150500.13.61.1
suse sle15kernel-source open
suse sle15kernel-source-azure fixed in 0:5.14.21-150500.33.60.1
suse sle15kernel-source-rt fixed in 0:5.14.21-150500.13.61.1
suse sle15kernel-syms fixed in 0:5.14.21-150500.55.73.1
suse sle15kernel-syms-azure fixed in 0:5.14.21-150500.33.60.1
suse sle15kernel-syms-rt fixed in 0:5.14.21-150500.13.61.1
suse sle15kernel-zfcpdump fixed in 0:5.14.21-150500.55.73.1
suse sle15ocfs2-kmp-rt fixed in 0:5.14.21-150500.13.61.1
suse sle15reiserfs-kmp-default fixed in 0:5.14.21-150500.55.73.1
▣
Scoring & Timeline
9.8
CRITICAL · CVSS v3.1 · 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
total
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
4msrcCVE-2022-48716
suse-csafSUSE-SU-2024:2939-1
suse-csafSUSE-SU-2024:2394-1
suse-csafSUSE-SU-2024:2372-1
🔗
References & Sources
3Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.