Security readout for executives and security teams
Plain-English summary
A hardware-specific PCIe flaw can corrupt data or hang applications or the processor on systems using affected Texas Instruments AM65x/DRA80xM revision 1.0 silicon. Linux lacked the required workaround. This is serious for exposed embedded or industrial systems, but it is not a general Linux vulnerability affecting unrelated hardware.
Executive priority
Treat this as a high-priority, hardware-scoped remediation. Immediately identify operational technology, appliances, or embedded systems using revision 1.0 silicon, then schedule validated kernel updates. Organizations without that hardware are unlikely to be exposed. The supplied evidence does not support an active-exploitation emergency.
Technical view
An inbound PCIe transaction spanning more than two internal 128-byte AXI bursts may be corrupted on affected silicon. The Linux PCI Keystone correction limits Maximum Read Request Size and Maximum Payload Size to 128 bytes. The supplied CVSS 3.1 score is 7.3, reflecting local, low-privilege impact to confidentiality, integrity, and availability.
Likely exposure
Exposure is limited to Linux systems using the relevant PCI Keystone controller on AM65x/DRA80xM silicon revision 1.0. Later silicon revisions are described as fixed. The bundle identifies several affected Linux versions through 6.11, but does not provide a clear branch-by-branch fixed-version table.
Exploitation context
The supplied CVSS vector describes local access, low complexity, low privileges, and no user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation. The condition may also arise operationally through qualifying PCIe traffic; malicious triggerability is not demonstrated here.
Researcher notes
This CVE addresses a Linux workaround for TI silicon erratum i2037 rather than a broadly applicable software defect. Researchers should distinguish hardware revision, controller use, and vendor backports from kernel version strings alone. The bundle's affected-version data is incomplete or ambiguous, so fixed status should be confirmed against the referenced commits and distribution guidance.
Mitigation direction
- Inventory systems using AM65x or DRA80xM revision 1.0 silicon and the Linux PCI Keystone driver.
- Install a vendor or distribution kernel confirmed to include the referenced i2037 workaround.
- Where upgrades are delayed, ask the platform vendor about safely enforcing 128-byte PCIe limits.
- Prioritize systems where processor hangs or corrupted PCIe data could disrupt critical operations.
Validation and detection
- Confirm the processor model and silicon revision from authoritative hardware inventory or platform documentation.
- Record each exposed system's kernel version, distribution build, and PCI Keystone driver usage.
- Verify the installed kernel contains the applicable referenced stable fix or vendor backport.
- After remediation, validate PCIe stability and workload integrity using approved platform testing.
- Monitor affected systems for unexplained PCIe errors, data corruption, application hangs, or processor hangs.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2024-47667 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H1.85.5LinuxVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/cfb006e185f64edbbdf7869eac352442bc76b8f6CVE reference, Linux
- https://git.kernel.org/stable/c/ebbdbbc580c1695dec283d0ba6448729dc993246CVE reference, Linux
- https://git.kernel.org/stable/c/135843c351c08df72bdd4b4ebea53c8052a76881CVE reference, Linux
- https://git.kernel.org/stable/c/af218c803fe298ddf00abef331aa526b20d7ea61CVE reference, Linux
- https://git.kernel.org/stable/c/576d0fb6f8d4bd4695e70eee173a1b9c7bae9572CVE reference, Linux
- https://git.kernel.org/stable/c/dd47051c76c8acd8cb983f01b4d1265da29cb66aCVE reference, Linux
- https://git.kernel.org/stable/c/86f271f22bbb6391410a07e08d6ca3757fda01faCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.