SECUFOCUSNOW
Home›CVE index›CVE-2024-36477
Review reviewHigh

CVE-2024-36477

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE 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 SPI_HDRSIZE to account for the header and use to allocate the transfer buffer.

CVSS
7.8
EPSS
0.22%
12.6% percentile
CISA KEV
Not listed
Published
2024.06.21
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.22%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE 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 SPI_HDRSIZE to account for the header and use to allocate the transfer buffer.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= a86a42ac2bd652fdc7836a9d880c306a2485c142 < 1547183852dcdfcc25878db7dd3620509217b0cd, >= a86a42ac2bd652fdc7836a9d880c306a2485c142 < de13c56f99477b56980c7e00b09c776d16b7563d, >= a86a42ac2bd652fdc7836a9d880c306a2485c142 < 195aba96b854dd664768f382cd1db375d8181f88, >= 6.6, > 6.6 < 6.6.33, > 6.7 < 6.9.4, 6.10
Fixed versions
6.6.33, 6.9.4

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-125