REDHAT-BUG-2507345: Medium severity Linux Kernel vulnerability

Published Jul 26, 2026
·
Updated

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

net/sched: clsapi: Handle TCACTCONSUMED in tcfqeventhandle

tcfclassify() can return TCACTCONSUMED while the skb is held by the defragmentation engine (e.g. actct on out-of-order fragments). When that happens the skb is no longer owned by the caller and must not be touched again.

tcfqeventhandle() did not handle TCACTCONSUMED: it fell through the switch and returned the skb to the caller as if classification had passed. The only qdisc that wires up qevents today is RED, via three call sites (qemark on REDPROBMARK/HARDMARK, qeearlydrop on congestiondrop) redenqueue() was continuing to operate on an skb it no longer owns in this case -- enqueueing it, dropping it, or updating statistics. Resulting in a UAF.

tc qdisc add dev eth0 root handle 1: red ... qevent earlydrop block 10 tc filter add block 10 ... action ct

(with ct defrag enabled and traffic that produces out-of-order fragments, e.g. a fragmented UDP stream)

Handle TCACTCONSUMED in tcfqeventhandle() the same way the ingress and egress fast paths do: treat it as stolen and return NULL without touching the skb. Unlike the TCACTSTOLEN case, the skb must not be dropped/freed here, as it is no longer owned by us.

Affected Software

1 affected component
Linux Kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Patch the kernel so that in net/sched/cls_api:Handle TC_ACT_CONSUMED in tcf_qevent_handle(), the function handles TC_ACT_CONSUMED the same way as the ingress TC_ACT_STOLEN case—i.e., for a consumed skb, return NULL and do not enqueue/drop/update statistics or touch the skb again.

    Linux kernel (net/sched) tcf_qevent_handle() handling of TC_ACT_CONSUMED = Handle TC_ACT_CONSUMED the same way as the ingress TC_ACT_STOLEN case (treat as consumed/stolen; return without further skb touch/enqueue/stats updates).

Event History

Jul 26, 2026
Data Sourced
via Red Hat·08:01 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2507345?

The severity of REDHAT-BUG-2507345 is rated as medium (4).

2

How do I fix REDHAT-BUG-2507345?

To fix REDHAT-BUG-2507345, update to the latest patched version of the Linux Kernel that addresses this vulnerability.

3

What software is affected by REDHAT-BUG-2507345?

The vulnerability REDHAT-BUG-2507345 affects the Linux Kernel.

4

What is the nature of the vulnerability described in REDHAT-BUG-2507345?

REDHAT-BUG-2507345 involves improper handling of TC_ACT_CONSUMED within the tcf_qevent_handle function during packet defragmentation.

5

When was REDHAT-BUG-2507345 published?

REDHAT-BUG-2507345 was published on July 26, 2026.

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