CVE-2024-53044

In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_api: fix xa_insert() error path in tcf_block_get_ext() This command: $ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact Error: block dev insert failed: -EBUSY. fails because user space requests the same block index to be set for both ingress and egress. [ side note, I don't think it even failed prior to commit 913b47d3424e ("net/sched: Introduce tc block netdev tracking infra"), because this is a command from an old set of notes of mine which used to work, but alas, I did not scientifically bisect this ] The problem is not that it fails, but rather, that the second time around, it fails differently (and irrecoverably): $ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact Error: dsa_core: Flow block cb is busy. [ another note: the extack is added by me for illustration purposes. the context of the problem is that clsact_init() obtains the same &q->ingress_block pointer as &q->egress_block, and since we call tcf_block_get_ext() on both of them, "dev" will be added to the block->ports xarray twice, thus failing the operation: once through the ingress block pointer, and once again through the egress block pointer. the problem itself is that when xa_insert() fails, we have emitted a FLOW_BLOCK_BIND command through ndo_setup_tc(), but the offload never sees a corresponding FLOW_BLOCK_UNBIND. ] Even correcting the bad user input, we still cannot recover: $ tc qdisc replace dev swp3 ingress_block 1 egress_block 2 clsact Error: dsa_core: Flow block cb is busy. Basically the only way to recover is to reboot the system, or unbind and rebind the net device driver. To fix the bug, we need to fill the correct error teardown path which was missed during code movement, and call tcf_block_offload_unbind() when xa_insert() fails. [ last note, fundamentally I blame the label naming convention in tcf_block_get_ext() for the bug. The labels should be named after what they do, not after the error path that jumps to them. This way, it is obviously wrong that two labels pointing to the same code mean something is wrong, and checking the code correctness at the goto site is also easier ]

• https://git.kernel.org/stable/c/8966eb69a143b1c032365fe84f2815f3c46f2590Patch
• https://git.kernel.org/stable/c/a13e690191eafc154b3f60afe9ce35aa9b9128b4Patch

Published

Nov 19, 2024

Last Modified

Aug 4, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2024-53033Memory corruption while doing Escape call when user provides…7.8
• CVE-2024-53034Memory corruption occurs during an Escape call if an invalid…7.8
• CVE-2024-5304Kofax Power PDF TGA File Parsing Out-Of-Bounds Write Remote …7.8
• CVE-2024-53041A vulnerability has been identified in Teamcenter Visualizat…7.8
• CVE-2024-53042In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-53043In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-53045In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-53046In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-53047In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-53048In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-53049In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-5305Kofax Power PDF PDF File Parsing Stack-based Buffer Overflow…7.8