LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26740: net/sched: act_mirred: use the backlog for mirred ingress

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can hang systems when specific traffic-control redirection sends traffic from egress back into ingress and hits a socket still holding its lock. The supplied sources describe reliability impact from deadlock, not data theft or remote code execution.

Executive priority

Treat as a reliability and availability concern for Linux networking hosts. Prioritize based on use of traffic control redirection and business criticality, because severity and exploitability data are incomplete.

Technical view

The flaw is in net/sched act_mirred handling for egress-to-ingress redirection. Inline receive-path processing could re-enter tcp_v4_rcv and deadlock on the originating socket lock. The fix uses the Rx backlog for all such reversals.

Likely exposure

Exposure is most likely on Linux systems using traffic control configurations with act_mirred ingress redirection. The bundle lists Linux kernel versions as affected but does not provide distribution-specific package status.

Exploitation context

The source bundle does not report active exploitation, and CISA KEV status is false. Evidence describes hangs in testing VMs about every ten runs and lockdep-reported tcp_v4_rcv deadlocks.

Researcher notes

The fix changes mirred ingress handling to enqueue reversed traffic through the Rx backlog instead of running the receive path inline. Supplied data lacks CVSS, CWE, public exploit evidence, and distro package mapping.

Mitigation direction

  • Upgrade to a Linux kernel or vendor package containing the referenced stable fixes.
  • Check distribution security advisories for CVE-2024-26740 backport status.
  • Where feasible, avoid affected mirred egress-to-ingress redirection until patched.
  • Prioritize patching hosts relying on Linux traffic control for production networking.

Validation and detection

  • Inventory Linux kernel versions across servers, containers hosts, and network appliances.
  • Review traffic control rules for act_mirred ingress redirect usage.
  • Confirm installed kernel includes the referenced stable commits or vendor backports.
  • Monitor affected systems for kernel hangs or lockdep tcp_v4_rcv deadlock reports.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26740 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux53592b3640019f2834701093e38272fdfd367ad8, 53592b3640019f2834701093e38272fdfd367ad8, 53592b3640019f2834701093e38272fdfd367ad8unaffected
LinuxLinux4.10, 0, 6.6.19, 6.7.7, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.