5.5

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

Modified
AliasesUBUNTU-CVE-2024-26740DEBIAN-CVE-2024-26740
Published 03-04-2024Last modified 30-10-2026

Vulnerability summary

CVE-2024-26740 is a medium (CVSS 5.5) Improper Locking vulnerability in linux. EPSS estimates a 0.18% chance of exploitation in the next 30 days, higher than 7.7% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.18%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 9 · Related 5

Timeline

  1. 03-04-2024
    PublishedVulnerability first disclosed.
  2. 30-10-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

4 scores · 3 sources · 2 versions

EPSS trend

Probability

0.18%

Chance of exploitation in the next 30 days

Percentile

8%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.18% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu116 products
  • linuxAll versions (No fix recorded)
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded)
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ 53592b3640019f2834701093e38272fdfd367ad8, < ac5c2ed6394c85f84877b1a1eec61cf004f90f4f | ≥ 53592b3640019f2834701093e38272fdfd367ad8, < 7c787888d164689da8b1b115f3ef562c1e843af4 | ≥ 53592b3640019f2834701093e38272fdfd367ad8, < 60ddea1600bc476e0f5e02bce0e29a460ccbf0be | ≥ 53592b3640019f2834701093e38272fdfd367ad8, < 52f671db18823089a02f07efc04efdb2272ddc17 | 4.10
  • linux_kernel≥ 4.10, < 6.6.19 | ≥ 6.7, < 6.7.7 | 6.8:rc1 | 6.8:rc2 | 6.8:rc3 | 6.8:rc4 | 6.8:rc5
Debian1 product
  • linuxAll versions (No fix recorded) | < 6.7.7-1

3 vendors · 119 products

References

8 links