# CVE-2022-3636: Linux Kernel Ethernet mtk_ppe.c __mtk_ppe_check_skb use after free

> A use-after-free vulnerability in the Linux Kernel Ethernet driver allows attackers with permissions to potentially execute code or escalate privileges.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **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:** No
- **Published:** 21 Oct 2022
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-wp33-7frp-g7vg, UBUNTU-CVE-2022-3636

## What is CVE-2022-3636?

CVE-2022-3636 is a medium-severity use after free vulnerability in Debian Debian Linux, published on 21 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in Linux Kernel 33fc42de33278b2b3ec6f3390512987bc29a62b7. This affects the function __mtk_ppe_check_skb of the file drivers/net/ethernet/mediatek/mtk_ppe.c of the component Ethernet Handler. Such manipulation leads to use after free. The name of the patch is 17a5f6a78dc7b8db385de346092d7d9f9dc24df6. It is best practice to apply a patch to resolve this issue. No released Linux Kernel version was ever affected by this CVE.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2022-3636?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2022-3636?

No fix has been published for CVE-2022-3636 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-3636 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3636 and fix it if it is affected.

What it is: CVE-2022-3636 is a medium-severity use after free vulnerability in Debian Debian Linux, published on 21 Oct 2022. 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-2022-3636 in the wild and no public exploit code.

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

## Sources

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

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