RHSA-2026:95587: Important: kpatch-patch-4_18_0-553_109_1, kpatch-patch-4_18_0-553_125_1, kpatch-patch-4_18_0-553_158_1, kpatch-patch-4_18_0-553_72_1, and kpatch-patch-4_18_0-553_85_1 security update

Published Nov 5, 2026
·
Updated

Important: kpatch-patch-4180-5531091, kpatch-patch-4180-5531251, kpatch-patch-4180-5531581, kpatch-patch-4180-553721, and kpatch-patch-4180-553851 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-4.18.0-553.109.1.el810.Security Fix(es): kernel: ipc: limit nextid allocation to the valid ID range (CVE-2026-52923) kernel: udp: fix potential use-after-free in tunnel segmentation (CVE-2026-74705) kernel: net: tun: bound receive headroom (CVE-2026-81000) 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

39 affected componentsFixes available
Red Hat Red Hat Enterprise Linux for Power, little endian - Extended Life Cycle
Red Hat Red Hat Enterprise Linux for Power, little endian
Red Hat Red Hat Enterprise Linux for x86_64
Red Hat Red Hat Enterprise Linux for x86_64 - Extended Life Cycle
redhat/kpatch-patch<4_18_0-553_109_1-1-15.el8_10
4_18_0-553_109_1-1-15.el8_10
redhat/kpatch-patch<4_18_0-553_125_1-1-12.el8_10
4_18_0-553_125_1-1-12.el8_10
redhat/kpatch-patch<4_18_0-553_158_1-1-4.el8_10
4_18_0-553_158_1-1-4.el8_10
redhat/kpatch-patch<4_18_0-553_72_1-1-19.el8_10
4_18_0-553_72_1-1-19.el8_10
redhat/kpatch-patch<4_18_0-553_85_1-1-17.el8_10
4_18_0-553_85_1-1-17.el8_10
redhat/kpatch-patch<4_18_0-553_109_1-1-15.el8_10
4_18_0-553_109_1-1-15.el8_10
redhat/kpatch-patch<4_18_0-553_109_1-debuginfo-1-15.el8_10
4_18_0-553_109_1-debuginfo-1-15.el8_10
redhat/kpatch-patch<4_18_0-553_109_1-debugsource-1-15.el8_10
4_18_0-553_109_1-debugsource-1-15.el8_10
redhat/kpatch-patch<4_18_0-553_125_1-1-12.el8_10
4_18_0-553_125_1-1-12.el8_10
redhat/kpatch-patch<4_18_0-553_125_1-debuginfo-1-12.el8_10
4_18_0-553_125_1-debuginfo-1-12.el8_10
redhat/kpatch-patch<4_18_0-553_125_1-debugsource-1-12.el8_10
4_18_0-553_125_1-debugsource-1-12.el8_10
redhat/kpatch-patch<4_18_0-553_158_1-1-4.el8_10
4_18_0-553_158_1-1-4.el8_10
redhat/kpatch-patch<4_18_0-553_158_1-debuginfo-1-4.el8_10
4_18_0-553_158_1-debuginfo-1-4.el8_10
redhat/kpatch-patch<4_18_0-553_158_1-debugsource-1-4.el8_10
4_18_0-553_158_1-debugsource-1-4.el8_10
redhat/kpatch-patch<4_18_0-553_72_1-1-19.el8_10
4_18_0-553_72_1-1-19.el8_10
redhat/kpatch-patch<4_18_0-553_72_1-debuginfo-1-19.el8_10
4_18_0-553_72_1-debuginfo-1-19.el8_10
redhat/kpatch-patch<4_18_0-553_72_1-debugsource-1-19.el8_10
4_18_0-553_72_1-debugsource-1-19.el8_10
redhat/kpatch-patch<4_18_0-553_85_1-1-17.el8_10
4_18_0-553_85_1-1-17.el8_10
redhat/kpatch-patch<4_18_0-553_85_1-debuginfo-1-17.el8_10
4_18_0-553_85_1-debuginfo-1-17.el8_10
redhat/kpatch-patch<4_18_0-553_85_1-debugsource-1-17.el8_10
4_18_0-553_85_1-debugsource-1-17.el8_10
redhat/kpatch-patch<4_18_0-553_109_1-1-15.el8_10
4_18_0-553_109_1-1-15.el8_10
redhat/kpatch-patch<4_18_0-553_109_1-debuginfo-1-15.el8_10
4_18_0-553_109_1-debuginfo-1-15.el8_10
redhat/kpatch-patch<4_18_0-553_109_1-debugsource-1-15.el8_10
4_18_0-553_109_1-debugsource-1-15.el8_10
redhat/kpatch-patch<4_18_0-553_125_1-1-12.el8_10
4_18_0-553_125_1-1-12.el8_10
redhat/kpatch-patch<4_18_0-553_125_1-debuginfo-1-12.el8_10
4_18_0-553_125_1-debuginfo-1-12.el8_10
redhat/kpatch-patch<4_18_0-553_125_1-debugsource-1-12.el8_10
4_18_0-553_125_1-debugsource-1-12.el8_10
redhat/kpatch-patch<4_18_0-553_158_1-1-4.el8_10
4_18_0-553_158_1-1-4.el8_10
redhat/kpatch-patch<4_18_0-553_158_1-debuginfo-1-4.el8_10
4_18_0-553_158_1-debuginfo-1-4.el8_10
redhat/kpatch-patch<4_18_0-553_158_1-debugsource-1-4.el8_10
4_18_0-553_158_1-debugsource-1-4.el8_10
redhat/kpatch-patch<4_18_0-553_72_1-1-19.el8_10
4_18_0-553_72_1-1-19.el8_10
redhat/kpatch-patch<4_18_0-553_72_1-debuginfo-1-19.el8_10
4_18_0-553_72_1-debuginfo-1-19.el8_10
redhat/kpatch-patch<4_18_0-553_72_1-debugsource-1-19.el8_10
4_18_0-553_72_1-debugsource-1-19.el8_10
redhat/kpatch-patch<4_18_0-553_85_1-1-17.el8_10
4_18_0-553_85_1-1-17.el8_10
redhat/kpatch-patch<4_18_0-553_85_1-debuginfo-1-17.el8_10
4_18_0-553_85_1-debuginfo-1-17.el8_10
redhat/kpatch-patch<4_18_0-553_85_1-debugsource-1-17.el8_10
4_18_0-553_85_1-debugsource-1-17.el8_10

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 4_18_0-553_109_1-1-15.el8_10
  2. Upgrade

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

    Fixed in 4_18_0-553_125_1-1-12.el8_10
  3. Upgrade

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

    Fixed in 4_18_0-553_158_1-1-4.el8_10
  4. Upgrade

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

    Fixed in 4_18_0-553_72_1-1-19.el8_10
  5. Upgrade

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

    Fixed in 4_18_0-553_85_1-1-17.el8_10
  6. Upgrade

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

    Fixed in 4_18_0-553_109_1-debuginfo-1-15.el8_10
  7. Upgrade

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

    Fixed in 4_18_0-553_109_1-debugsource-1-15.el8_10
  8. Upgrade

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

    Fixed in 4_18_0-553_125_1-debuginfo-1-12.el8_10
  9. Upgrade

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

    Fixed in 4_18_0-553_125_1-debugsource-1-12.el8_10
  10. Upgrade

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

    Fixed in 4_18_0-553_158_1-debuginfo-1-4.el8_10
  11. Upgrade

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

    Fixed in 4_18_0-553_158_1-debugsource-1-4.el8_10
  12. Upgrade

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

    Fixed in 4_18_0-553_72_1-debuginfo-1-19.el8_10
  13. Upgrade

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

    Fixed in 4_18_0-553_72_1-debugsource-1-19.el8_10
  14. Upgrade

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

    Fixed in 4_18_0-553_85_1-debuginfo-1-17.el8_10
  15. Upgrade

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

    Fixed in 4_18_0-553_85_1-debugsource-1-17.el8_10
  16. Upgrade

    Upgrade kernel to a version that resolves this vulnerability.

    Fixed in 4.18.0-553.109.1.el8_10Patch kpatch-patch-4_18_0-553_109_1
  17. Upgrade

    Upgrade kernel to a version that resolves this vulnerability.

    Patch kpatch-patch-4_18_0-553_125_1
  18. Upgrade

    Upgrade kernel to a version that resolves this vulnerability.

    Patch kpatch-patch-4_18_0-553_158_1
  19. Upgrade

    Upgrade kernel to a version that resolves this vulnerability.

    Patch kpatch-patch-4_18_0-553_72_1
  20. Upgrade

    Upgrade kernel to a version that resolves this vulnerability.

    Patch kpatch-patch-4_18_0-553_85_1

Event History

Nov 5, 2026
Advisory Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionAffected Software
Advisory Published
via Red Hat·03:56 PM
Data Sourced
via Red Hat·03:56 PM
Severity

Frequently Asked Questions

1

Can this live patch module be used with any RHEL 8 kernel?

No. The module described is targeted specifically for kernel-4.18.0-553.109.1.el8_10; compatibility with other kernel builds is not stated.

2

How is this update applied?

It is a kernel live patch module that can be loaded with the kpatch command-line utility to modify the code of a running kernel.

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