CVE-2026-99612: ALSA: hda/tas2781: Only accept CRC-less V1 data if all entries are valid

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ALSA: hda/tas2781: Only accept CRC-less V1 data if all entries are valid

Commit 408249089c48 ("ALSA: hda/tas2781: Accept V1 calibration data without CRC") only checked the first device entry. On machines where the BIOS populates fewer entries than p->ndev, the remaining all-zero entries are applied and tas2781calipreproc() divides by zero on playback open.

Accept CRC-less V1 data only if every expected entry is non-zero and self-consistent (R0 1/R0 close to 1.0), otherwise reject it as before.

Affected Software

5 affected componentsFixes available
linux/kernel>=6.18.57<6.18.64
6.18.64
linux/kernel>=7.2.11<7.3
7.3
linux/kernel>=7.3.0<7.3.5
7.3.5
debian/linux*
debian/linux<=7.3.4-1
6.1.176-16.1.192-26.12.107-16.12.117-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1
  5. Compensating control

    For CRC-less V1 calibration data, accept it only when every expected device entry is non-zero and self-consistent (R0 × 1/R0 is close to 1.0); otherwise reject it.

Event History

Nov 20, 2026
CVE Published
via MITRE·05:49 AM
Data Sourced
via MITRE·05:49 AM
Description
Data Sourced
via OSV·05:49 AM
DescriptionAffected Software
Data Sourced
via NVD·06:17 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel TAS2781 HDA audio driver are affected when they accept CRC-less V1 calibration data and the BIOS provides fewer calibration entries than the number of expected devices.

2

What triggers the failure?

The failure occurs when playback is opened after incomplete BIOS calibration data leaves expected device entries as all zeros. Those zero-valued entries are applied, causing tas2781_cali_preproc() to divide by zero.

3

What validation is required for CRC-less V1 calibration data after the fix?

Every expected entry must be non-zero and self-consistent, with R0 multiplied by its reciprocal close to 1.0. If any expected entry fails these checks, the CRC-less V1 data is rejected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203