What is CVE-2024-26740?

CVE-2024-26740 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Improper Locking flaw (CWE-667), affecting Linux kernel versions from 4.10 onward and patched in 6.6.19, 6.7.7 and 6.8. CVE-2024-26740 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2024-26740?

CVE-2024-26740 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2024-26740?

Yes, CVE-2024-26740 has been patched. Fixed versions include 6.6.19, 6.7.7 and 6.8. If you are running Linux kernel 4.10 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2024-26740 actively exploited?

CVE-2024-26740 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Improper Locking (CWE-667)?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/667.html

CVE-2024-26740

Medium

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.

Package Linux Kernel

Published 2024-04-03

Last modified 2025-03-17

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

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

Weakness type

CWE-667

CVE-2024-26740 is a Improper Locking vulnerability

What is Improper Locking?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. Learn more on MITRE CWE

Affected versions

Linux kernel versions 4.10 and later are affected. Fixed in 6.6.19, 6.7.7, 6.8 and their respective stable series.

Affected from

≥ 4.10

Fixed in

✓ 6.6.19 6.6.x ✓ 6.7.7 6.7.x ✓ 6.8

References

3 total

Kernel Git
https://git.kernel.org/stable/c/52f671db18823089a02f07efc04efdb2272ddc17

Patch
Kernel Git
https://git.kernel.org/stable/c/60ddea1600bc476e0f5e02bce0e29a460ccbf0be

Patch
Kernel Git
https://git.kernel.org/stable/c/7c787888d164689da8b1b115f3ef562c1e843af4

Patch

Details

CVE ID CVE-2024-26740

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2024-04-03

Modified 2025-03-17

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2024-26740?

CVE-2024-26740 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Improper Locking flaw (CWE-667) . It affects Linux kernel versions from 4.10 onward and has been patched in 6.6.19, 6.7.7 and 6.8. CVE-2024-26740 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2024-26740?

CVE-2024-26740 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2024-26740?

Yes. CVE-2024-26740 has been patched. Fixed versions include 6.6.19, 6.7.7 and 6.8. If you are running Linux kernel 4.10 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2024-26740 actively exploited?

No. CVE-2024-26740 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.