CVE-2024-26740
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-667
- Record status
- Modified
Affected
- Linux Kernel < 6.6.19
- Linux Kernel < 6.7.7
- Linux Kernel 6.8
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-26740.md and follow it. Check whether this project is affected by CVE-2024-26740. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/52f671db18823089a02f07efc04efdb2272ddc17
- https://git.kernel.org/stable/c/60ddea1600bc476e0f5e02bce0e29a460ccbf0be
- https://git.kernel.org/stable/c/7c787888d164689da8b1b115f3ef562c1e843af4
- https://git.kernel.org/stable/c/52f671db18823089a02f07efc04efdb2272ddc17
- https://git.kernel.org/stable/c/60ddea1600bc476e0f5e02bce0e29a460ccbf0be
- https://git.kernel.org/stable/c/7c787888d164689da8b1b115f3ef562c1e843af4
References
- https://git.kernel.org/stable/c/52f671db18823089a02f07efc04efdb2272ddc17
- https://git.kernel.org/stable/c/60ddea1600bc476e0f5e02bce0e29a460ccbf0be
- https://git.kernel.org/stable/c/7c787888d164689da8b1b115f3ef562c1e843af4
- https://git.kernel.org/stable/c/ac5c2ed6394c85f84877b1a1eec61cf004f90f4f
- https://git.kernel.org/stable/c/52f671db18823089a02f07efc04efdb2272ddc17
- https://git.kernel.org/stable/c/60ddea1600bc476e0f5e02bce0e29a460ccbf0be
- https://git.kernel.org/stable/c/7c787888d164689da8b1b115f3ef562c1e843af4