# CVE-2024-47667: PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)

> A hardware errata in specific TI processors can cause system hangs when processing large PCIe packets, requiring a kernel workaround to limit payload sizes.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-47667, DEBIAN-CVE-2024-47667, GHSA-9jfw-gm57-mv43, ROOT-OS-DEBIAN-11-CVE-2024-47667, UBUNTU-CVE-2024-47667

## What is CVE-2024-47667?

CVE-2024-47667 is a high-severity denial of service vulnerability in Linux kernel, published on 9 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)

Errata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0
(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an
inbound PCIe TLP spans more than two internal AXI 128-byte bursts,
the bus may corrupt the packet payload and the corrupt data may
cause associated applications or the processor to hang.

The workaround for Errata #i2037 is to limit the maximum read
request size and maximum payload size to 128 bytes. Add workaround
for Errata #i2037 here.

The errata and workaround is applicable only to AM65x SR 1.0 and
later versions of the silicon will have this fixed.

[1] -> https://www.ti.com/lit/er/sprz452i/sprz452i.pdf

## Which versions are affected by CVE-2024-47667?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-47667?

Apply the vendor's patch.

## Is CVE-2024-47667 being exploited?

There is no known exploitation of CVE-2024-47667 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47667 and fix it if it is affected.

What it is: CVE-2024-47667 is a high-severity denial of service vulnerability in Linux kernel, published on 9 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47667 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47667/ (Markdown: https://insights.sbomify.com/CVE-2024-47667/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47667
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47667
- OSV: https://osv.dev/vulnerability/CVE-2024-47667

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47667/
Summaries are generated and may contain mistakes; the official description above is the record.