Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 52f671db18823089a02f07efc04efdb2272ddc17, 60ddea1600bc476e0f5e02bce0e29a460ccbf0be, 7c787888d164689da8b1b115f3ef562c1e843af4.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 52f671db18823089a02f07efc04efdb2272ddc17, 60ddea1600bc476e0f5e02bce0e29a460ccbf0be, 7c787888d164689da8b1b115f3ef562c1e843af4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 3, 2024
Updated
Oct 30, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-26740

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.10 and later · before 6.6.19
  • linux linux kernel6.7 and later · before 6.7.7
  • linux linux kernel6.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.10affected
    • 53592b3640019f2834701093e38272fdfd367ad8 and later · before ac5c2ed6394c85f84877b1a1eec61cf004f90f4faffected · git
    • 53592b3640019f2834701093e38272fdfd367ad8 and later · before 7c787888d164689da8b1b115f3ef562c1e843af4affected · git
    • 53592b3640019f2834701093e38272fdfd367ad8 and later · before 60ddea1600bc476e0f5e02bce0e29a460ccbf0beaffected · git
    • 53592b3640019f2834701093e38272fdfd367ad8 and later · before 52f671db18823089a02f07efc04efdb2272ddc17affected · git
    • before 4.10not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.19 and later · up to and including 6.6.*not affected · semver
    • 6.7.7 and later · up to and including 6.7.*not affected · semver
    • 6.8 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.7.7-16.7.7-1
Red Hat:rhel_eus:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.57.1.el9_40:7.3.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-develbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-develbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-develbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-devel-matchedbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-docbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-tools-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4

+56

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26779Apr 3, 2024 · wifi: mac80211: fix race condition on enabling fast-xmit
    35Monitor
  • ← EarlierCVE-2024-26690Apr 3, 2024 · net: stmmac: protect updates of 64-bit statistics counters
    30Monitor
  • Later →CVE-2024-26772Apr 3, 2024 · ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux52f671db18823089a02f07efc04efdb2272ddc17Vendor (CNA)
Linux Linux60ddea1600bc476e0f5e02bce0e29a460ccbf0beVendor (CNA)
Linux Linux7c787888d164689da8b1b115f3ef562c1e843af4Vendor (CNA)
Linux Linuxac5c2ed6394c85f84877b1a1eec61cf004f90f4fVendor (CNA)
debian:linux6.7.7-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records