# net/sched: Fix mirred deadlock on device recursion

CVE record · `CVE-2024-27010`

- **Identifiers:** `CVE-2024-27010`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2024
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2024, 05:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `e578d9c02587d57bfa7b560767c698a668a468c6 to before 09d2e807aeb8e4f2e5eac4a3064f28dcf19b9c1e` (git)
  - affected: `e578d9c02587d57bfa7b560767c698a668a468c6 to before 524323f52cbfbac4fe3f8a33a8cc405fafba0d33` (git)
  - affected: `e578d9c02587d57bfa7b560767c698a668a468c6 to before e6b90468da4dae2281a6e381107f411efb48b0ef` (git)
  - affected: `e578d9c02587d57bfa7b560767c698a668a468c6 to before 0f022d32c3eca477fbf79a205243a6123ed0fe11` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.2`
  - unaffected: `before 4.2` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.156 to 6.6.*, inclusive` (semver)
  - unaffected: `6.8.8 to 6.8.*, inclusive` (semver)
  - unaffected: `6.9 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's net/sched mirred action can deadlock when a packet is mirrored or redirected back to the same device through a classful egress qdisc. Kernels from 4.2 until the fixes are affected. An attacker who can configure traffic control rules can trigger the deadlock. Upgrade to 6.1.191, 6.6.156, 6.8.8, 6.9 or a later version.

Written 13 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0018, the 7th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 1 May 2024. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2024-27010](https://www.cve.org/CVERecord?id=CVE-2024-27010)
- [NVD: CVE-2024-27010](https://nvd.nist.gov/vuln/detail/CVE-2024-27010)

### References from the CNA

- <https://git.kernel.org/stable/c/09d2e807aeb8e4f2e5eac4a3064f28dcf19b9c1e>
- <https://git.kernel.org/stable/c/524323f52cbfbac4fe3f8a33a8cc405fafba0d33>
- <https://git.kernel.org/stable/c/e6b90468da4dae2281a6e381107f411efb48b0ef>
- <https://git.kernel.org/stable/c/0f022d32c3eca477fbf79a205243a6123ed0fe11>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2024-27010>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2024-27010/>. Everything for agents: <https://agentprime.io/llms.txt>.
