# CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG

> A flaw in the TI AM65 CPSW driver allows out-of-bounds memory access due to incorrect port ID extraction, leading to kernel crashes.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** AZL-97797, BELL-CVE-2026-74737, DEBIAN-CVE-2026-74737, GHSA-582m-3r7c-4438, UBUNTU-CVE-2026-74737

## What is CVE-2026-74737?

CVE-2026-74737 is a critical memory corruption vulnerability in Linux, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG

On the packet reception path, the ID of the MAC Port on which the packet
was received, is embedded in the RX DMA Descriptor's metadata. The ID is
extracted using the helper function cppi5_desc_get_tags_ids() which fills
in the 16-bit Source Tag into the 'port_id' variable. However, it is only
the lower 8-bits of the 16-bit Source Tag that represent the MAC Port ID,
while the upper 8-bits are Hardware-Reserved and carry an arbitrary value.
With the existing logic, sporadic kernel crash is observed due to the
subsequent driver code accessing out-of-bound memory because of an invalid
port_id.

Hence, fix the port_id extraction logic to use only the lower 8-bits of the
Source Tag as the MAC Port ID.

## Which versions are affected by CVE-2026-74737?


## How do I fix CVE-2026-74737?

Apply the vendor's patch.

## Is CVE-2026-74737 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74737 and fix it if it is affected.

What it is: CVE-2026-74737 is a critical memory corruption vulnerability in Linux, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74737 in the wild and no public exploit code.

Affected product: Linux. 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-2026-74737/ (Markdown: https://insights.sbomify.com/CVE-2026-74737/index.md)
```

## Sources

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

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