# CVE-2025-22107: net: dsa: sja1105: fix kasan out-of-bounds warning in sja1105_table_delete_entry()

> An out-of-bounds memory access in the sja1105 DSA driver can cause a kernel crash, requiring a patch to prevent denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 16 Apr 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-62507, AZL-69596, BELL-CVE-2025-22107, DEBIAN-CVE-2025-22107, GHSA-v43g-xqqr-j4r8, ROOT-OS-DEBIAN-11-CVE-2025-22107, ROOT-OS-DEBIAN-12-CVE-2025-22107, ROOT-OS-DEBIAN-13-CVE-2025-22107, ROOT-OS-UBUNTU-2204-CVE-2025-22107, ROOT-OS-UBUNTU-2404-CVE-2025-22107, UBUNTU-CVE-2025-22107

## What is CVE-2025-22107?

CVE-2025-22107 is a high-severity memory corruption vulnerability in Linux kernel, published on 16 Apr 2025. 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: fix kasan out-of-bounds warning in sja1105_table_delete_entry()

There are actually 2 problems:
- deleting the last element doesn't require the memmove of elements
  [i + 1, end) over it. Actually, element i+1 is out of bounds.
- The memmove itself should move size - i - 1 elements, because the last
  element is out of bounds.

The out-of-bounds element still remains out of bounds after being
accessed, so the problem is only that we touch it, not that it becomes
in active use. But I suppose it can lead to issues if the out-of-bounds
element is part of an unmapped page.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-22107?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-22107?

Apply the vendor's patch.

## Is CVE-2025-22107 being exploited?

There is no known exploitation of CVE-2025-22107 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-2025-22107 and fix it if it is affected.

What it is: CVE-2025-22107 is a high-severity memory corruption vulnerability in Linux kernel, published on 16 Apr 2025. 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-2025-22107 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-2025-22107/ (Markdown: https://insights.sbomify.com/CVE-2025-22107/index.md)
```

## Sources

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

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