CVE-2022-48889

What it actually does

The module alias string generated for the sof-nau8825 platform device exceeds the 20-character limit (including NUL) in platform_device_id entries, resulting in invalid characters in the MODULE_ALIAS macro during compilation of snd-soc-sof_nau8825.

Why it matters to the business

Kernel builds for affected Intel audio configurations fail, delaying deployment of updates or custom kernels across Linux distributions and embedded systems with high downstream usage.

How an attack unfolds

No runtime exploitation path exists; the issue manifests only at build time when the module alias overflows and produces illegal encoding in the generated .mod.c file.

How to fix it

Update to a kernel containing commit fba1b23befd88366fe646787b3797e64d7338fd2 or later; replace long platform device names with shorter unique aliases under 19 characters.

How to confirm the fix worked

Confirm the fix by verifying that the MODULE_ALIAS strings in snd-soc-sof_nau8825.mod.c are 20 characters or shorter and that the build completes without encoding errors.

Typical attack path

1. Trigger kernel build with CONFIG_SND_SOC_INTEL_SOF_NAU8825 configured
2. Compilation reaches MODULE_ALIAS generation for the platform device
3. Build fails with -Winvalid-source-encoding error due to length overflow

How to detect it

Review kernel build logs for MODULE_ALIAS generation errors referencing sof_nau8825 or adl_max98373_nau8825; no runtime indicators apply.

What your security team should do

• Apply the referenced commit or equivalent backport to all maintained kernel trees immediately
• Audit custom kernel configurations that enable sof-nau8825 audio drivers
• Monitor build logs for MODULE_ALIAS length warnings in future kernel compiles