RHSA-2026:33219: Important: kpatch-patch-4_18_0-477_107_1, kpatch-patch-4_18_0-477_120_1, kpatch-patch-4_18_0-477_130_1, kpatch-patch-4_18_0-477_143_1, and kpatch-patch-4_18_0-477_97_1 security update

Published Jun 29, 2026
·
Updated

Important: kpatch-patch-4180-4771071, kpatch-patch-4180-4771201, kpatch-patch-4180-4771301, kpatch-patch-4180-4771431, and kpatch-patch-4180-477971 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-477.97.1.el88.Security Fix(es): kernel: net/sched: actpedit: extend the writable skb range per key (CVE-2026-46331) kernel: Linux kernel: smb: client: reject userspace cifs.spnego descriptions (CVE-2026-46243) 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

38 affected componentsFixes available
Red Hat Red Hat Enterprise Linux for x86_64 - Update Services for SAP Solutions
Red Hat Red Hat Enterprise Linux for x86_64 - Extended Update Support Extension
Red Hat Red Hat Enterprise Linux Server for Power LE - Update Services for SAP Solutions
redhat/kpatch-patch<4_18_0-477_107_1-1-8.el8_8
4_18_0-477_107_1-1-8.el8_8
redhat/kpatch-patch<4_18_0-477_120_1-1-7.el8_8
4_18_0-477_120_1-1-7.el8_8
redhat/kpatch-patch<4_18_0-477_130_1-1-5.el8_8
4_18_0-477_130_1-1-5.el8_8
redhat/kpatch-patch<4_18_0-477_143_1-1-2.el8_8
4_18_0-477_143_1-1-2.el8_8
redhat/kpatch-patch<4_18_0-477_97_1-1-12.el8_8
4_18_0-477_97_1-1-12.el8_8
redhat/kpatch-patch<4_18_0-477_107_1-1-8.el8_8
4_18_0-477_107_1-1-8.el8_8
redhat/kpatch-patch<4_18_0-477_107_1-debuginfo-1-8.el8_8
4_18_0-477_107_1-debuginfo-1-8.el8_8
redhat/kpatch-patch<4_18_0-477_107_1-debugsource-1-8.el8_8
4_18_0-477_107_1-debugsource-1-8.el8_8
redhat/kpatch-patch<4_18_0-477_120_1-1-7.el8_8
4_18_0-477_120_1-1-7.el8_8
redhat/kpatch-patch<4_18_0-477_120_1-debuginfo-1-7.el8_8
4_18_0-477_120_1-debuginfo-1-7.el8_8
redhat/kpatch-patch<4_18_0-477_120_1-debugsource-1-7.el8_8
4_18_0-477_120_1-debugsource-1-7.el8_8
redhat/kpatch-patch<4_18_0-477_130_1-1-5.el8_8
4_18_0-477_130_1-1-5.el8_8
redhat/kpatch-patch<4_18_0-477_130_1-debuginfo-1-5.el8_8
4_18_0-477_130_1-debuginfo-1-5.el8_8
redhat/kpatch-patch<4_18_0-477_130_1-debugsource-1-5.el8_8
4_18_0-477_130_1-debugsource-1-5.el8_8
redhat/kpatch-patch<4_18_0-477_143_1-1-2.el8_8
4_18_0-477_143_1-1-2.el8_8
redhat/kpatch-patch<4_18_0-477_143_1-debuginfo-1-2.el8_8
4_18_0-477_143_1-debuginfo-1-2.el8_8
redhat/kpatch-patch<4_18_0-477_143_1-debugsource-1-2.el8_8
4_18_0-477_143_1-debugsource-1-2.el8_8
redhat/kpatch-patch<4_18_0-477_97_1-1-12.el8_8
4_18_0-477_97_1-1-12.el8_8
redhat/kpatch-patch<4_18_0-477_97_1-debuginfo-1-12.el8_8
4_18_0-477_97_1-debuginfo-1-12.el8_8
redhat/kpatch-patch<4_18_0-477_97_1-debugsource-1-12.el8_8
4_18_0-477_97_1-debugsource-1-12.el8_8
redhat/kpatch-patch<4_18_0-477_107_1-1-8.el8_8
4_18_0-477_107_1-1-8.el8_8
redhat/kpatch-patch<4_18_0-477_107_1-debuginfo-1-8.el8_8
4_18_0-477_107_1-debuginfo-1-8.el8_8
redhat/kpatch-patch<4_18_0-477_107_1-debugsource-1-8.el8_8
4_18_0-477_107_1-debugsource-1-8.el8_8
redhat/kpatch-patch<4_18_0-477_120_1-1-7.el8_8
4_18_0-477_120_1-1-7.el8_8
redhat/kpatch-patch<4_18_0-477_120_1-debuginfo-1-7.el8_8
4_18_0-477_120_1-debuginfo-1-7.el8_8
redhat/kpatch-patch<4_18_0-477_120_1-debugsource-1-7.el8_8
4_18_0-477_120_1-debugsource-1-7.el8_8
redhat/kpatch-patch<4_18_0-477_130_1-1-5.el8_8
4_18_0-477_130_1-1-5.el8_8
redhat/kpatch-patch<4_18_0-477_130_1-debuginfo-1-5.el8_8
4_18_0-477_130_1-debuginfo-1-5.el8_8
redhat/kpatch-patch<4_18_0-477_130_1-debugsource-1-5.el8_8
4_18_0-477_130_1-debugsource-1-5.el8_8
redhat/kpatch-patch<4_18_0-477_143_1-1-2.el8_8
4_18_0-477_143_1-1-2.el8_8
redhat/kpatch-patch<4_18_0-477_143_1-debuginfo-1-2.el8_8
4_18_0-477_143_1-debuginfo-1-2.el8_8
redhat/kpatch-patch<4_18_0-477_143_1-debugsource-1-2.el8_8
4_18_0-477_143_1-debugsource-1-2.el8_8
redhat/kpatch-patch<4_18_0-477_97_1-1-12.el8_8
4_18_0-477_97_1-1-12.el8_8
redhat/kpatch-patch<4_18_0-477_97_1-debuginfo-1-12.el8_8
4_18_0-477_97_1-debuginfo-1-12.el8_8
redhat/kpatch-patch<4_18_0-477_97_1-debugsource-1-12.el8_8
4_18_0-477_97_1-debugsource-1-12.el8_8

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-477_107_1-1-8.el8_8
  2. Upgrade

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

    Fixed in 4_18_0-477_120_1-1-7.el8_8
  3. Upgrade

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

    Fixed in 4_18_0-477_130_1-1-5.el8_8
  4. Upgrade

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

    Fixed in 4_18_0-477_143_1-1-2.el8_8
  5. Upgrade

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

    Fixed in 4_18_0-477_97_1-1-12.el8_8
  6. Upgrade

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

    Fixed in 4_18_0-477_107_1-debuginfo-1-8.el8_8
  7. Upgrade

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

    Fixed in 4_18_0-477_107_1-debugsource-1-8.el8_8
  8. Upgrade

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

    Fixed in 4_18_0-477_120_1-debuginfo-1-7.el8_8
  9. Upgrade

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

    Fixed in 4_18_0-477_120_1-debugsource-1-7.el8_8
  10. Upgrade

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

    Fixed in 4_18_0-477_130_1-debuginfo-1-5.el8_8
  11. Upgrade

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

    Fixed in 4_18_0-477_130_1-debugsource-1-5.el8_8
  12. Upgrade

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

    Fixed in 4_18_0-477_143_1-debuginfo-1-2.el8_8
  13. Upgrade

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

    Fixed in 4_18_0-477_143_1-debugsource-1-2.el8_8
  14. Upgrade

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

    Fixed in 4_18_0-477_97_1-debuginfo-1-12.el8_8
  15. Upgrade

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

    Fixed in 4_18_0-477_97_1-debugsource-1-12.el8_8
  16. Upgrade

    Upgrade Linux kernel (kernel-4.18.0-477.97.1.el8_8) to a version that resolves this vulnerability.

    Patch kpatch-patch-4_18_0-477_97_1
  17. Upgrade

    Upgrade Linux kernel (kernel-4.18.0-477.97.1.el8_8) to a version that resolves this vulnerability.

    Patch kpatch-patch-4_18_0-477_107_1
  18. Upgrade

    Upgrade Linux kernel (kernel-4.18.0-477.97.1.el8_8) to a version that resolves this vulnerability.

    Patch kpatch-patch-4_18_0-477_120_1
  19. Upgrade

    Upgrade Linux kernel (kernel-4.18.0-477.97.1.el8_8) to a version that resolves this vulnerability.

    Patch kpatch-patch-4_18_0-477_130_1
  20. Upgrade

    Upgrade Linux kernel (kernel-4.18.0-477.97.1.el8_8) to a version that resolves this vulnerability.

    Patch kpatch-patch-4_18_0-477_143_1

Event History

Jun 29, 2026
Advisory Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionAffected Software
Advisory Published
via Red Hat·07:04 PM
Data Sourced
via Red Hat·07:04 PM
Severity

Frequently Asked Questions

1

What is the severity of RHSA-2026:33219?

The severity of RHSA-2026:33219 is high, rated at level 7.

2

How do I fix RHSA-2026:33219?

To fix RHSA-2026:33219, you should apply the necessary security updates for the kpatch-patch modules immediately.

3

What software is affected by RHSA-2026:33219?

RHSA-2026:33219 affects the kpatch-patch for Red Hat Enterprise Linux for x86_64 and Power LE architectures.

4

What are the patches included in RHSA-2026:33219?

RHSA-2026:33219 includes the kpatch-patch versions 4_18_0-477_107_1, 4_18_0-477_120_1, 4_18_0-477_130_1, 4_18_0-477_143_1, and 4_18_0-477_97_1.

5

When was RHSA-2026:33219 published?

RHSA-2026:33219 was published on June 29, 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