# CVE-2025-68338: net: dsa: microchip: Don't free uninitialized ksz_irq

> A use-after-free vulnerability in the Microchip DSA driver allows local attackers to cause a denial of service by triggering an error path that frees uninitialized IRQ resources.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-72983, BELL-CVE-2025-68338, DEBIAN-CVE-2025-68338, GHSA-4mf7-7hx2-42fv, ROOT-OS-DEBIAN-13-CVE-2025-68338, ROOT-OS-UBUNTU-2404-CVE-2025-68338, UBUNTU-CVE-2025-68338

## What is CVE-2025-68338?

CVE-2025-68338 is an use after free vulnerability in Linux, published on 23 Dec 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: microchip: Don't free uninitialized ksz_irq

If something goes wrong at setup, ksz_irq_free() can be called on
uninitialized ksz_irq (for example when ksz_ptp_irq_setup() fails). It
leads to freeing uninitialized IRQ numbers and/or domains.

Use dsa_switch_for_each_user_port_continue_reverse() in the error path
to iterate only over the fully initialized ports.

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


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

Apply the vendor's patch.

## Is CVE-2025-68338 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68338 and fix it if it is affected.

What it is: CVE-2025-68338 is an use after free vulnerability in Linux, published on 23 Dec 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-68338 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-2025-68338/ (Markdown: https://insights.sbomify.com/CVE-2025-68338/index.md)
```

## Sources

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

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