# CVE-2024-35889: idpf: fix kernel panic on unknown packet types

> A missing network layer handler assignment in the idpf driver causes a kernel panic when processing unknown packet types, leading to denial of service.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 19 May 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-35889, DEBIAN-CVE-2024-35889, GHSA-fp96-cm52-3v96, UBUNTU-CVE-2024-35889

## What is CVE-2024-35889?

CVE-2024-35889 is a high-severity vulnerability in Linux kernel, published on 19 May 2024. 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:

idpf: fix kernel panic on unknown packet types

In the very rare case where a packet type is unknown to the driver,
idpf_rx_process_skb_fields would return early without calling
eth_type_trans to set the skb protocol / the network layer handler.
This is especially problematic if tcpdump is running when such a
packet is received, i.e. it would cause a kernel panic.

Instead, call eth_type_trans for every single packet, even when
the packet type is unknown.

## Which versions are affected by CVE-2024-35889?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-35889?

Apply the vendor's patch.

## Is CVE-2024-35889 being exploited?

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

What it is: CVE-2024-35889 is a high-severity vulnerability in Linux kernel, published on 19 May 2024. 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-2024-35889 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-2024-35889/ (Markdown: https://insights.sbomify.com/CVE-2024-35889/index.md)
```

## Sources

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

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