LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50051: ASoC: SOF: debug: Fix potential buffer overflow by snprintf()

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: debug: 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.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel flaw in ASoC SOF debug handling. A formatting function could report a length larger than the destination buffer, creating a potential overflow if that return value is reused. The upstream note calls exploitation unrealistic, and no CVSS score is provided.

Executive priority

Handle through normal kernel patch management unless vendor guidance raises severity. There is no supplied evidence of active exploitation, but kernel memory-safety fixes still deserve timely remediation on managed Linux fleets.

Technical view

The fix changes snprintf() to scnprintf() in Linux kernel ASoC SOF debug code because snprintf() returns the would-be length on truncation. Reusing that value can allow later writes past the intended buffer boundary. The source bundle lists affected Linux kernel versions including 5.11, 5.15.63, 5.19.4, and 6.0.

Likely exposure

Exposure is most likely on systems running affected Linux kernel builds that include the ASoC SOF debug code. Practical exposure depends on kernel configuration, distribution backports, and whether the relevant audio debug path is reachable in the environment.

Exploitation context

The provided sources do not show active exploitation, public weaponization, or KEV listing. The kernel description describes the overflow scenario as potential and unrealistic. Treat exploitability as unproven from the supplied evidence.

Researcher notes

Key uncertainty is reachability. The CVE text identifies a return-value misuse risk, not a demonstrated exploit path. Validate affected kernel lineage, configuration, and vendor backport status before rating environment-specific risk.

Mitigation direction

  • Apply Linux vendor kernel updates containing the upstream stable fix.
  • Confirm whether your distribution has backported the scnprintf() change.
  • Prioritize internet-facing or multi-user systems if affected kernels are present.
  • Track vendor advisories for severity, package names, and reboot requirements.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and appliances.
  • Check whether affected systems include ASoC SOF debug code.
  • Compare installed kernel changelogs against the referenced stable commits.
  • Verify remediated systems boot into the updated kernel.
Prepared
Confidence
medium
Sources
5

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-2022-50051 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
4Source 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
LinuxLinux5b10b62989219aa527ee4fa555d1995a3b70981b, 5b10b62989219aa527ee4fa555d1995a3b70981b, 5b10b62989219aa527ee4fa555d1995a3b70981bunaffected
LinuxLinux5.11, 0, 5.15.63, 5.19.4, 6.0affected
Weakness

CWE details

No CWE listed

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