CVE-2024-36477: tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1547183852dcdfcc25878db7dd3620509217b0cd, 195aba96b854dd664768f382cd1db375d8181f88, de13c56f99477b56980c7e00b09c776d16b7563d; Azure Linux 3.0 ARM 6.6.35.1-4; Azure Linux 3.0 x64 6.6.35.1-4.
Low priority for now. Upgrade to Linux Linux 1547183852dcdfcc25878db7dd3620509217b0cd, 195aba96b854dd664768f382cd1db375d8181f88, de13c56f99477b56980c7e00b09c776d16b7563d; Azure Linux 3.0 ARM 6.6.35.1-4; Azure Linux 3.0 x64 6.6.35.1-4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 21, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-125
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.6affected
- a86a42ac2bd652fdc7836a9d880c306a2485c142 and later · before 1547183852dcdfcc25878db7dd3620509217b0cdaffected · git
- a86a42ac2bd652fdc7836a9d880c306a2485c142 and later · before de13c56f99477b56980c7e00b09c776d16b7563daffected · git
- a86a42ac2bd652fdc7836a9d880c306a2485c142 and later · before 195aba96b854dd664768f382cd1db375d8181f88affected · git
- before 6.6not affected · semver
- 6.6.33 and later · up to and including 6.6.*not affected · semver
- 6.9.4 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelafter 6.6 · before 6.6.33
- linux linux kernelafter 6.7 · before 6.9.4
- linux linux kernel6.10
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.9.7-1 | 6.9.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-38637Jun 21, 2024 · greybus: lights: check return of get_channel_from_mode22Monitor
- ← EarlierCVE-2024-34777Jun 21, 2024 · dma-mapping: benchmark: fix node id validation28Monitor
- Later →CVE-2024-36481Jun 21, 2024 · tracing/probes: fix error check in parse_btf_field()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1547183852dcdfcc25878db7dd3620509217b0cd | Vendor (CNA) |
| Linux Linux | 195aba96b854dd664768f382cd1db375d8181f88 | Vendor (CNA) |
| Linux Linux | de13c56f99477b56980c7e00b09c776d16b7563d | Vendor (CNA) |
| Azure Linux 3.0 ARM | 6.6.35.1-4 · kernel | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 6.6.35.1-4 · kernel | Microsoft (MSRC) |
| CBL Mariner 2.0 ARM | 5.15.160.1-1 · kernel | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 5.15.160.1-1 · kernel | Microsoft (MSRC) |
| debian:linux | 6.9.7-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.