CVE-2022-50050: ASoC: SOF: Intel: hda: Fix potential buffer overflow by snprintf()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 6ee1310f4d148dbf04c4159b88afd0b941018903, 94c1ceb043c1a002de9649bb630c8e8347645982, f7915c5614a7ece117ec390f21a410531eac48de.
Low priority for now. Upgrade to Linux Linux 6ee1310f4d148dbf04c4159b88afd0b941018903, 94c1ceb043c1a002de9649bb630c8e8347645982, f7915c5614a7ece117ec390f21a410531eac48de or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: hda: Fix potential buffer overflow by snprintf() snprintf() returns the would-be-filled size when the string overflows the given buffer size, hence using this value may result in the buffer overflow (although it's unrealistic). This patch replaces with a safer version, scnprintf() for papering over such a potential issue.
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10 and later · before 5.15.63
- linux linux kernel5.16 and later · before 5.19.4
- linux linux kernel6.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.10affected
- 29c8e4398f02adacd429c7847dacc8aea5a0c2f1 and later · before 6ee1310f4d148dbf04c4159b88afd0b941018903affected · git
- 29c8e4398f02adacd429c7847dacc8aea5a0c2f1 and later · before f7915c5614a7ece117ec390f21a410531eac48deaffected · git
- 29c8e4398f02adacd429c7847dacc8aea5a0c2f1 and later · before 94c1ceb043c1a002de9649bb630c8e8347645982affected · git
- before 5.10not affected · semver
- 5.15.63 and later · up to and including 5.15.*not affected · semver
- 5.19.4 and later · up to and including 5.19.*not affected · semver
- 6.0 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.19.6-1 | 5.19.6-1 |
| Red Hat:rhel_aus:8.4::baseos | bpftool | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | bpftool-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-abi-stablelists | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-core | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-core | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-devel | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-modules | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debug-modules-extra | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-debuginfo-common-x86_64 | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-devel | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-doc | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-modules | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-modules-extra | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-tools | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-tools-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | kernel-tools-libs | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | perf | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | perf-debuginfo | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
| Red Hat:rhel_aus:8.4::baseos | python3-perf | before 0:4.18.0-305.179.1.el8_4 | 0:4.18.0-305.179.1.el8_4 |
+85
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50048Jun 18, 2025 · netfilter: nf_tables: possible module reference underflow in error path22Monitor
- ← EarlierCVE-2022-50049Jun 18, 2025 · ASoC: DPCM: Don't pick up BE without substream22Monitor
- Later →CVE-2022-50051Jun 18, 2025 · ASoC: SOF: debug: Fix potential buffer overflow by snprintf()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 6ee1310f4d148dbf04c4159b88afd0b941018903 | Vendor (CNA) |
| Linux Linux | 94c1ceb043c1a002de9649bb630c8e8347645982 | Vendor (CNA) |
| Linux Linux | f7915c5614a7ece117ec390f21a410531eac48de | Vendor (CNA) |
| debian:linux | 5.19.6-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-rt | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-debuginfo | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-devel | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-kvm | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules-extra | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo-common-x86_64 | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
| red hat:kernel-rt-devel | 0:5.14.0-70.151.1.rt21.223.el9_0 · Red Hat:rhel_e4s:9.0::nfv | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.