# net/sched: act_mirred: use the backlog for mirred ingress

CVE record · `CVE-2024-26740`

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

Published by the CVE Program (CNA: Linux) at 3 Apr 2024, 17:00 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: `53592b3640019f2834701093e38272fdfd367ad8 to before ac5c2ed6394c85f84877b1a1eec61cf004f90f4f` (git)
  - affected: `53592b3640019f2834701093e38272fdfd367ad8 to before 7c787888d164689da8b1b115f3ef562c1e843af4` (git)
  - affected: `53592b3640019f2834701093e38272fdfd367ad8 to before 60ddea1600bc476e0f5e02bce0e29a460ccbf0be` (git)
  - affected: `53592b3640019f2834701093e38272fdfd367ad8 to before 52f671db18823089a02f07efc04efdb2272ddc17` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.10`
  - unaffected: `before 4.10` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.19 to 6.6.*, inclusive` (semver)
  - unaffected: `6.7.7 to 6.7.*, inclusive` (semver)
  - unaffected: `6.8 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 net/sched act_mirred component is affected from version 4.10 until fixed. Redirecting traffic from egress to ingress can cause a deadlock in the TCP receive path that hangs the system, and the source gives few details on what an attacker needs. Upgrade to 6.1.191 or later in the 6.1 series, 6.6.19 or later in 6.6, 6.7.7 or later in 6.7, or 6.8 or later.

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 3 Apr 2024. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/ac5c2ed6394c85f84877b1a1eec61cf004f90f4f>
- <https://git.kernel.org/stable/c/7c787888d164689da8b1b115f3ef562c1e843af4>
- <https://git.kernel.org/stable/c/60ddea1600bc476e0f5e02bce0e29a460ccbf0be>
- <https://git.kernel.org/stable/c/52f671db18823089a02f07efc04efdb2272ddc17>

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-26740>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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