RHSA-2020:4331: Important: kpatch-patch security update

Published Oct 26, 2020
·
Updated

This is a kernel live patch module which is automatically loaded by the RPM post-install script to modify the code of a running kernel.Security Fix(es): kernel: metadata validator in XFS may cause an inode with a valid, user-creatable extended attribute to be flagged as corrupt (CVE-2020-14385) kernel: memory corruption in net/packet/afpacket.c leads to elevation of privilege (CVE-2020-14386) 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.

Affected Software

42 affected componentsFixes available
redhat/kpatch-patch<4_18_0-193-1-7.el8
4_18_0-193-1-7.el8
redhat/kpatch-patch<4_18_0-193_13_2-1-2.el8_2
4_18_0-193_13_2-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-1-2.el8_2
4_18_0-193_14_3-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-2.el8_2
4_18_0-193_19_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_1_2-1-5.el8_2
4_18_0-193_1_2-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-1-4.el8_2
4_18_0-193_6_3-1-4.el8_2
redhat/kpatch-patch<4_18_0-193-1-7.el8
4_18_0-193-1-7.el8
redhat/kpatch-patch<4_18_0-193-debuginfo-1-7.el8
4_18_0-193-debuginfo-1-7.el8
redhat/kpatch-patch<4_18_0-193-debugsource-1-7.el8
4_18_0-193-debugsource-1-7.el8
redhat/kpatch-patch<4_18_0-193_13_2-1-2.el8_2
4_18_0-193_13_2-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debuginfo-1-2.el8_2
4_18_0-193_13_2-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debugsource-1-2.el8_2
4_18_0-193_13_2-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-1-2.el8_2
4_18_0-193_14_3-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debuginfo-1-2.el8_2
4_18_0-193_14_3-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debugsource-1-2.el8_2
4_18_0-193_14_3-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-2.el8_2
4_18_0-193_19_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debuginfo-1-2.el8_2
4_18_0-193_19_1-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debugsource-1-2.el8_2
4_18_0-193_19_1-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_1_2-1-5.el8_2
4_18_0-193_1_2-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_1_2-debuginfo-1-5.el8_2
4_18_0-193_1_2-debuginfo-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_1_2-debugsource-1-5.el8_2
4_18_0-193_1_2-debugsource-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-1-4.el8_2
4_18_0-193_6_3-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-debuginfo-1-4.el8_2
4_18_0-193_6_3-debuginfo-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-debugsource-1-4.el8_2
4_18_0-193_6_3-debugsource-1-4.el8_2
redhat/kpatch-patch<4_18_0-193-1-7.el8
4_18_0-193-1-7.el8
redhat/kpatch-patch<4_18_0-193-debuginfo-1-7.el8
4_18_0-193-debuginfo-1-7.el8
redhat/kpatch-patch<4_18_0-193-debugsource-1-7.el8
4_18_0-193-debugsource-1-7.el8
redhat/kpatch-patch<4_18_0-193_13_2-1-2.el8_2
4_18_0-193_13_2-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debuginfo-1-2.el8_2
4_18_0-193_13_2-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_13_2-debugsource-1-2.el8_2
4_18_0-193_13_2-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-1-2.el8_2
4_18_0-193_14_3-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debuginfo-1-2.el8_2
4_18_0-193_14_3-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_14_3-debugsource-1-2.el8_2
4_18_0-193_14_3-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-1-2.el8_2
4_18_0-193_19_1-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debuginfo-1-2.el8_2
4_18_0-193_19_1-debuginfo-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_19_1-debugsource-1-2.el8_2
4_18_0-193_19_1-debugsource-1-2.el8_2
redhat/kpatch-patch<4_18_0-193_1_2-1-5.el8_2
4_18_0-193_1_2-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_1_2-debuginfo-1-5.el8_2
4_18_0-193_1_2-debuginfo-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_1_2-debugsource-1-5.el8_2
4_18_0-193_1_2-debugsource-1-5.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-1-4.el8_2
4_18_0-193_6_3-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-debuginfo-1-4.el8_2
4_18_0-193_6_3-debuginfo-1-4.el8_2
redhat/kpatch-patch<4_18_0-193_6_3-debugsource-1-4.el8_2
4_18_0-193_6_3-debugsource-1-4.el8_2

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-193-1-7.el8
  2. Upgrade

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

    Fixed in 4_18_0-193_13_2-1-2.el8_2
  3. Upgrade

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

    Fixed in 4_18_0-193_14_3-1-2.el8_2
  4. Upgrade

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

    Fixed in 4_18_0-193_19_1-1-2.el8_2
  5. Upgrade

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

    Fixed in 4_18_0-193_1_2-1-5.el8_2
  6. Upgrade

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

    Fixed in 4_18_0-193_6_3-1-4.el8_2
  7. Upgrade

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

    Fixed in 4_18_0-193-debuginfo-1-7.el8
  8. Upgrade

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

    Fixed in 4_18_0-193-debugsource-1-7.el8
  9. Upgrade

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

    Fixed in 4_18_0-193_13_2-debuginfo-1-2.el8_2
  10. Upgrade

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

    Fixed in 4_18_0-193_13_2-debugsource-1-2.el8_2
  11. Upgrade

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

    Fixed in 4_18_0-193_14_3-debuginfo-1-2.el8_2
  12. Upgrade

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

    Fixed in 4_18_0-193_14_3-debugsource-1-2.el8_2
  13. Upgrade

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

    Fixed in 4_18_0-193_19_1-debuginfo-1-2.el8_2
  14. Upgrade

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

    Fixed in 4_18_0-193_19_1-debugsource-1-2.el8_2
  15. Upgrade

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

    Fixed in 4_18_0-193_1_2-debuginfo-1-5.el8_2
  16. Upgrade

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

    Fixed in 4_18_0-193_1_2-debugsource-1-5.el8_2
  17. Upgrade

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

    Fixed in 4_18_0-193_6_3-debuginfo-1-4.el8_2
  18. Upgrade

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

    Fixed in 4_18_0-193_6_3-debugsource-1-4.el8_2

Event History

Jun 16, 2026
Advisory Published
via Red Hat·03:09 PM
Data Sourced
via Red Hat·03:09 PM
RemedyDescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2020:4331?

The severity of RHSA-2020:4331 is considered moderate as it addresses a vulnerability in the kernel live patch module.

2

How do I fix RHSA-2020:4331?

To fix RHSA-2020:4331, you should update your kpatch-patch package to the recommended versions specified in the advisory.

3

Which versions of kpatch-patch are affected by RHSA-2020:4331?

RHSA-2020:4331 affects multiple versions of kpatch-patch, and specific versions are listed in the advisory.

4

What types of issues does RHSA-2020:4331 address?

RHSA-2020:4331 addresses a vulnerability in the XFS file system's metadata validator that may incorrectly flag inodes.

5

Is it safe to ignore the patch for RHSA-2020:4331?

It is not safe to ignore the patch for RHSA-2020:4331, as failing to apply the update may leave your system vulnerable to exploitation.

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