Skip to content
OpenAdvisories
High RLSA-2026:49212 3 CVEs

Important: kernel security update

Published Aug 2, 2026 · Updated Aug 2, 2026

Summary

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

* kernel: ipc: limit next_id allocation to the valid ID range (CVE-2026-52923)

* kernel: tipc: fix double-free in tipc_buf_append() (CVE-2026-52993)

* kernel: net: sched: UAF via missing handler for TC_ACT_CONSUMED in tcf_qevent_handle ()

* kernel: net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle (CVE-2026-64530)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Fixed packages 1

ReleasePackageFixed in
Rocky Linux · 9 kernel 0:5.14.0-687.33.1.el9_8

Vulnerabilities 3

  • Critical 9.8
    CVE-2026-52993 Public exploit

    tipc: fix double-free in tipc_buf_append()

    In the Linux kernel, the following vulnerability has been resolved: tipc: fix double-free in tipc_buf_append() tipc_msg_validate() can potentially reallocate the skb it is validating, freeing the old one. In tipc_buf_append(), it was being called with a point…

  • Critical 9.8

    net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle

    In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle tcf_classify() can return TC_ACT_CONSUMED while the skb is held by the defragmentation engine (e.g. act_ct on out-of-order frag…

  • High 7.8
    CVE-2026-52923 Public exploit

    ipc: limit next_id allocation to the valid ID range

    In the Linux kernel, the following vulnerability has been resolved: ipc: limit next_id allocation to the valid ID range The checkpoint/restore sysctl path can request the next SysV IPC id through ids->next_id. ipc_idr_alloc() currently forwards that request t…

References

  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2492094
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2492437
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2504052