RHSA-2026:56224: Important: kpatch-patch-5_14_0-427_100_1, kpatch-patch-5_14_0-427_113_1, kpatch-patch-5_14_0-427_126_1, kpatch-patch-5_14_0-427_68_2, and kpatch-patch-5_14_0-427_84_1 security update

Published Aug 18, 2026
·
Updated

Important: kpatch-patch-5140-4271001, kpatch-patch-5140-4271131, kpatch-patch-5140-4271261, kpatch-patch-5140-427682, and kpatch-patch-5140-427841 security update

Other sources

This is a kernel live patch module which can be loaded by the kpatch command line utility to modify the code of a running kernel. This patch module is targeted for kernel-5.14.0-427.68.2.el94.Security Fix(es): kernel: ipv6: icmp: clear skb2->cb[] in ip6errgenicmpv6unreach() (CVE-2026-43038) kernel: dlm: validate length in dlmsearchrsbtree (CVE-2026-43125) kernel: netfilter: flowtable: strictly check for maximum number of actions (CVE-2026-43329) kernel: net: sched: UAF via missing handler for TCACTCONSUMED in tcfqeventhandle (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.

Red Hat

Affected Software

40 affected componentsFixes available
Red Hat Red Hat Enterprise Linux Server for Power LE - Update Services for SAP Solutions
Red Hat Red Hat Enterprise Linux for x86_64 - Extended Life Cycle
Red Hat Red Hat Enterprise Linux Server - AUS
Red Hat Red Hat Enterprise Linux for Power, little endian - Extended Life Cycle
Red Hat Red Hat Enterprise Linux for x86_64 - Update Services for SAP Solutions
redhat/kpatch-patch<5_14_0-427_100_1-1-12.el9_4
5_14_0-427_100_1-1-12.el9_4
redhat/kpatch-patch<5_14_0-427_113_1-1-10.el9_4
5_14_0-427_113_1-1-10.el9_4
redhat/kpatch-patch<5_14_0-427_126_1-1-7.el9_4
5_14_0-427_126_1-1-7.el9_4
redhat/kpatch-patch<5_14_0-427_68_2-1-19.el9_4
5_14_0-427_68_2-1-19.el9_4
redhat/kpatch-patch<5_14_0-427_84_1-1-14.el9_4
5_14_0-427_84_1-1-14.el9_4
redhat/kpatch-patch<5_14_0-427_100_1-1-12.el9_4
5_14_0-427_100_1-1-12.el9_4
redhat/kpatch-patch<5_14_0-427_100_1-debuginfo-1-12.el9_4
5_14_0-427_100_1-debuginfo-1-12.el9_4
redhat/kpatch-patch<5_14_0-427_100_1-debugsource-1-12.el9_4
5_14_0-427_100_1-debugsource-1-12.el9_4
redhat/kpatch-patch<5_14_0-427_113_1-1-10.el9_4
5_14_0-427_113_1-1-10.el9_4
redhat/kpatch-patch<5_14_0-427_113_1-debuginfo-1-10.el9_4
5_14_0-427_113_1-debuginfo-1-10.el9_4
redhat/kpatch-patch<5_14_0-427_113_1-debugsource-1-10.el9_4
5_14_0-427_113_1-debugsource-1-10.el9_4
redhat/kpatch-patch<5_14_0-427_126_1-1-7.el9_4
5_14_0-427_126_1-1-7.el9_4
redhat/kpatch-patch<5_14_0-427_126_1-debuginfo-1-7.el9_4
5_14_0-427_126_1-debuginfo-1-7.el9_4
redhat/kpatch-patch<5_14_0-427_126_1-debugsource-1-7.el9_4
5_14_0-427_126_1-debugsource-1-7.el9_4
redhat/kpatch-patch<5_14_0-427_68_2-1-19.el9_4
5_14_0-427_68_2-1-19.el9_4
redhat/kpatch-patch<5_14_0-427_68_2-debuginfo-1-19.el9_4
5_14_0-427_68_2-debuginfo-1-19.el9_4
redhat/kpatch-patch<5_14_0-427_68_2-debugsource-1-19.el9_4
5_14_0-427_68_2-debugsource-1-19.el9_4
redhat/kpatch-patch<5_14_0-427_84_1-1-14.el9_4
5_14_0-427_84_1-1-14.el9_4
redhat/kpatch-patch<5_14_0-427_84_1-debuginfo-1-14.el9_4
5_14_0-427_84_1-debuginfo-1-14.el9_4
redhat/kpatch-patch<5_14_0-427_84_1-debugsource-1-14.el9_4
5_14_0-427_84_1-debugsource-1-14.el9_4
redhat/kpatch-patch<5_14_0-427_100_1-1-12.el9_4
5_14_0-427_100_1-1-12.el9_4
redhat/kpatch-patch<5_14_0-427_100_1-debuginfo-1-12.el9_4
5_14_0-427_100_1-debuginfo-1-12.el9_4
redhat/kpatch-patch<5_14_0-427_100_1-debugsource-1-12.el9_4
5_14_0-427_100_1-debugsource-1-12.el9_4
redhat/kpatch-patch<5_14_0-427_113_1-1-10.el9_4
5_14_0-427_113_1-1-10.el9_4
redhat/kpatch-patch<5_14_0-427_113_1-debuginfo-1-10.el9_4
5_14_0-427_113_1-debuginfo-1-10.el9_4
redhat/kpatch-patch<5_14_0-427_113_1-debugsource-1-10.el9_4
5_14_0-427_113_1-debugsource-1-10.el9_4
redhat/kpatch-patch<5_14_0-427_126_1-1-7.el9_4
5_14_0-427_126_1-1-7.el9_4
redhat/kpatch-patch<5_14_0-427_126_1-debuginfo-1-7.el9_4
5_14_0-427_126_1-debuginfo-1-7.el9_4
redhat/kpatch-patch<5_14_0-427_126_1-debugsource-1-7.el9_4
5_14_0-427_126_1-debugsource-1-7.el9_4
redhat/kpatch-patch<5_14_0-427_68_2-1-19.el9_4
5_14_0-427_68_2-1-19.el9_4
redhat/kpatch-patch<5_14_0-427_68_2-debuginfo-1-19.el9_4
5_14_0-427_68_2-debuginfo-1-19.el9_4
redhat/kpatch-patch<5_14_0-427_68_2-debugsource-1-19.el9_4
5_14_0-427_68_2-debugsource-1-19.el9_4
redhat/kpatch-patch<5_14_0-427_84_1-1-14.el9_4
5_14_0-427_84_1-1-14.el9_4
redhat/kpatch-patch<5_14_0-427_84_1-debuginfo-1-14.el9_4
5_14_0-427_84_1-debuginfo-1-14.el9_4
redhat/kpatch-patch<5_14_0-427_84_1-debugsource-1-14.el9_4
5_14_0-427_84_1-debugsource-1-14.el9_4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_100_1-1-12.el9_4
  2. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_113_1-1-10.el9_4
  3. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_126_1-1-7.el9_4
  4. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_68_2-1-19.el9_4
  5. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_84_1-1-14.el9_4
  6. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_100_1-debuginfo-1-12.el9_4
  7. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_100_1-debugsource-1-12.el9_4
  8. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_113_1-debuginfo-1-10.el9_4
  9. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_113_1-debugsource-1-10.el9_4
  10. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_126_1-debuginfo-1-7.el9_4
  11. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_126_1-debugsource-1-7.el9_4
  12. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_68_2-debuginfo-1-19.el9_4
  13. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_68_2-debugsource-1-19.el9_4
  14. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_84_1-debuginfo-1-14.el9_4
  15. Upgrade

    Upgrade redhat/kpatch-patch to a version that resolves this vulnerability.

    Fixed in 5_14_0-427_84_1-debugsource-1-14.el9_4
  16. Upgrade

    Upgrade kernel-5.14.0-427.68.2.el9_4 to a version that resolves this vulnerability.

    Patch kpatch-patch-5_14_0-427_100_1
  17. Upgrade

    Upgrade kernel-5.14.0-427.68.2.el9_4 to a version that resolves this vulnerability.

    Patch kpatch-patch-5_14_0-427_113_1
  18. Upgrade

    Upgrade kernel-5.14.0-427.68.2.el9_4 to a version that resolves this vulnerability.

    Patch kpatch-patch-5_14_0-427_126_1
  19. Upgrade

    Upgrade kernel-5.14.0-427.68.2.el9_4 to a version that resolves this vulnerability.

    Patch kpatch-patch-5_14_0-427_68_2
  20. Upgrade

    Upgrade kernel-5.14.0-427.68.2.el9_4 to a version that resolves this vulnerability.

    Patch kpatch-patch-5_14_0-427_84_1

Event History

Aug 18, 2026
Advisory Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionAffected Software
Advisory Published
via Red Hat·02:43 PM
Data Sourced
via Red Hat·02:43 PM
Severity

Frequently Asked Questions

1

How can I determine whether this live patch module applies to a system?

This live patch module is targeted for the running kernel kernel-5.14.0-427.68.2.el9_4. Systems running that kernel should be assessed for applicability of this module.

2

Is there a remediation option that does not require immediately replacing the running kernel?

The module can be loaded with the kpatch command-line utility to modify code in a running kernel. This provides a way to apply the live patch without replacing the running kernel at that time.

3

Which platform families are identified by the advisory?

The advisory lists Red Hat Enterprise Linux offerings for x86_64 and Power little-endian, including Extended Life Cycle, AUS, and Update Services for SAP Solutions. Applicability also depends on the targeted kernel release.

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