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

Published Apr 3, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

net/sched: actmirred: use the backlog for mirred ingress

The Linux kernel CVE team has assigned CVE-2024-26740 to this issue.

Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024040300-CVE-2024-26740-4d6f@gregkh/T

Other sources

In the Linux kernel, the following vulnerability has been resolved:

net/sched: actmirred: use the backlog for mirred ingress

The test Davide added in commit ca22da2fbd69 ("actmirred: use the backlog for nested calls to mirred ingress") hangs our testing VMs every 10 or so runs, with the familiar tcpv4rcv -> tcpv4rcv 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.

NVD

Affected Software

15 affected componentsFixes available
Linux Linux kernel>=4.10<6.6.19
Linux Linux kernel>=6.7<6.7.7
Linux Linux kernel=6.8-rc1
Linux Linux kernel=6.8-rc2
Linux Linux kernel=6.8-rc3
Linux Linux kernel=6.8-rc4
Linux Linux kernel=6.8-rc5
IBM Security Verify Governance<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Software Stack<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Virtual Appliance<=ISVG 10.0.2
IBM Security Verify Governance Identity Manager Container<=ISVG 10.0.2
redhat/kernel<6.6.19
6.6.19
redhat/kernel<6.7.7
6.7.7
redhat/kernel<6.8
6.8
Microsoft cbl2 kernel 5.15.186.1-1

Event History

Apr 3, 2024
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Apr 4, 2024
Data Sourced
via Red Hat·01:29 AM
DescriptionSeverityAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·12:29 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·12:29 AM
Affected Software
Updated
via Microsoft·12:29 AM
DescriptionSeverity

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-26740?

CVE-2024-26740 has been classified as a moderate severity vulnerability in the Linux kernel.

2

How do I fix CVE-2024-26740?

To mitigate CVE-2024-26740, upgrade the Linux kernel to version 6.6.19, 6.7.7, or 6.8.

3

Which versions of the Linux kernel are affected by CVE-2024-26740?

CVE-2024-26740 affects Linux kernel versions from 4.10 up to, but not including, 6.6.19 and also impacts pre-release versions of 6.8.

4

Is there a workaround for CVE-2024-26740?

Currently, there is no confirmed workaround for CVE-2024-26740 aside from updating the kernel.

5

What impact does CVE-2024-26740 have on system security?

CVE-2024-26740 could potentially allow for undesirable behavior in network traffic scheduling, affecting overall system security and performance.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203