# CVE-2026-97435: net: dsa: sja1105: flower: reject cross-chip redirect

> A local attacker can trigger an out-of-bounds access or incorrect port redirection in the sja1105 DSA driver by configuring cross-chip flower rules.

- **Severity:** Not scored
- **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:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103799, BELL-CVE-2026-97435, DEBIAN-CVE-2026-97435, GHSA-fv9v-g8xq-3w88, UBUNTU-CVE-2026-97435

## What is CVE-2026-97435?

CVE-2026-97435 is a memory corruption vulnerability in Linux, published on 24 Sep 2026. 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:

net: dsa: sja1105: flower: reject cross-chip redirect

dsa_port_from_netdev() may return a valid port from a different switch
chip. Programming another chip's port index into the local hardware
causes redirection to the wrong port, or an out-of-bounds access if the
index exceeds the local chip's port count.

Apply a minimal fix that adds a check to catch this case and adjusts the
extack message. When cls->common.skip_sw is not set, the operation could
instead redirect to the upstream port and let the software or upstream
switch(es) handle the forward, but that is not addressed here.

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


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

Apply the vendor's patch.

## Is CVE-2026-97435 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97435 is a memory corruption vulnerability in Linux, published on 24 Sep 2026. 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-2026-97435 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-97435/ (Markdown: https://insights.sbomify.com/CVE-2026-97435/index.md)
```

## Sources

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

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