LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48889: ASoC: Intel: sof-nau8825: fix module alias overflow

In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: sof-nau8825: fix module alias overflow The maximum name length for a platform_device_id entry is 20 characters including the trailing NUL byte. The sof_nau8825.c file exceeds that, which causes an obscure error message: sound/soc/intel/boards/snd-soc-sof_nau8825.mod.c:35:45: error: illegal character encoding in string literal [-Werror,-Winvalid-source-encoding] MODULE_ALIAS("platform:adl_max98373_nau8825<U+0018><AA>"); ^~~~ include/linux/module.h:168:49: note: expanded from macro 'MODULE_ALIAS' ^~~~~~ include/linux/module.h:165:56: note: expanded from macro 'MODULE_INFO' ^~~~ include/linux/moduleparam.h:26:47: note: expanded from macro '__MODULE_INFO' = __MODULE_INFO_PREFIX __stringify(tag) "=" info I could not figure out how to make the module handling robust enough to handle this better, but as a quick fix, using slightly shorter names that are still unique avoids the build 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 CVE describes a Linux kernel build problem in an Intel audio driver. An internal module alias name was too long, causing malformed module metadata and build failures. The provided sources do not show a path to compromise a running system.

Executive priority

Treat as low operational urgency unless your teams build affected Linux kernels or maintain kernel-derived products. Prioritize routine patch tracking over emergency response because the cited evidence points to build reliability, not known exploitation.

Technical view

The ASoC Intel sof-nau8825 driver exceeded the 20-character platform_device_id name limit, including the trailing NUL byte. The overflow affected generated MODULE_ALIAS data and produced an invalid string literal during builds. The upstream fix shortened the identifiers while preserving uniqueness.

Likely exposure

Exposure appears limited to Linux kernel source trees or builds that include the affected Intel sof-nau8825 ASoC board driver versions listed in the CVE source bundle. Organizations using vendor-supplied kernels should confirm whether their vendor backported the fix.

Exploitation context

The source bundle does not report active exploitation, KEV listing, public exploit activity, CVSS scoring, or a runtime attack primitive. The described impact is a build-time failure caused by malformed generated module alias data.

Researcher notes

Evidence is narrow: the CVE record describes a platform_device_id length violation and a fix using shorter unique names. No CWE, CVSS, exploit status, or broader affected hardware details are provided in the bundle.

Mitigation direction

  • Check vendor kernel advisories for CVE-2022-48889 backport status.
  • Update to a kernel package containing the referenced stable fixes.
  • For custom kernels, apply the upstream identifier-shortening fix.
  • Track affected build pipelines that compile the sof-nau8825 driver.

Validation and detection

  • Compare kernel source or package changelog against the referenced stable commits.
  • Review build logs for MODULE_ALIAS invalid string errors in sof_nau8825 outputs.
  • Confirm whether sof-nau8825 support is included in your kernel configuration.
  • Check that vendor guidance marks CVE-2022-48889 fixed or not applicable.
Prepared
Confidence
high
Sources
4

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-48889 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
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8d0872f6239f9d067d538d8368bdec643bb0d255, 8d0872f6239f9d067d538d8368bdec643bb0d255unaffected
LinuxLinux5.17, 0, 6.1.7, 6.2affected
Weakness

CWE details

No CWE listed

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