CVE-2024-36477: tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer

Published Jun 21, 2024
·
Updated

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

tpmtisspi: Account for SPI header when allocating TPM SPI xfer buffer

The Linux kernel CVE team has assigned CVE-2024-36477 to this issue.

Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024062150-CVE-2024-36477-7063@gregkh/T

Other sources

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

tpmtisspi: Account for SPI header when allocating TPM SPI xfer buffer

The TPM SPI transfer mechanism uses MAXSPIFRAMESIZE for computing the maximum transfer length and the size of the transfer buffer. As such, it does not account for the 4 bytes of header that prepends the SPI data frame. This can result in out-of-bounds accesses and was confirmed with KASAN.

Introduce SPIHDRSIZE to account for the header and use to allocate the transfer buffer.

NVD

Affected Software

16 affected componentsFixes available
redhat/kernel<6.6.33
6.6.33
redhat/kernel<6.9.4
6.9.4
redhat/kernel<6.10
6.10
Linux Linux kernel<6.6.0
Linux Linux kernel>=6.6.1<6.6.33
Linux Linux kernel>=6.9<6.9.4
Linux Linux kernel=6.10.0-rc1
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
Linux Linux kernel>6.6<6.6.33
Linux Linux kernel>6.7<6.9.4
Linux Linux kernel=6.10-rc1
Microsoft azl3 kernel 6.6.35.1-4
Microsoft azl3 kernel 6.6.29.1-5
Microsoft cbl2 kernel 5.15.180.1-1
Microsoft cbl2 kernel 5.15.180.1-1
Microsoft cbl2 kernel 5.15.160.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.6.33
  2. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.9.4
  3. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.10
  4. Upgrade

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

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1

Event History

Jun 21, 2024
CVE Published
via MITRE·11:18 AM
Data Sourced
via MITRE·11:18 AM
DescriptionSeverity
Data Sourced
via NVD·12:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 12, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Sep 11, 2024
Data Sourced
via Launchpad·04:24 PM
Description
Nov 30, 2024
Data Sourced
via Ubuntu·04:43 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-36477?

CVE-2024-36477 has been classified with a severity rating that indicates a potential security risk to systems using the affected Linux kernel versions.

2

How do I fix CVE-2024-36477?

To remediate CVE-2024-36477, upgrade the Linux kernel to version 6.6.33, 6.9.4, or 6.10 depending on your system's configuration.

3

Which Linux kernel versions are affected by CVE-2024-36477?

CVE-2024-36477 affects Linux kernel versions prior to 6.6.33, 6.9.4, and 6.10.

4

Is CVE-2024-36477 specific to any particular distribution?

CVE-2024-36477 is documented for the Red Hat kernel and Debian Linux packages among others using vulnerable kernel versions.

5

What can happen if CVE-2024-36477 is not addressed?

Failing to address CVE-2024-36477 may expose systems to security vulnerabilities that can be exploited by malicious actors.

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