RHSA-2026:51134: Moderate: systemd security, bug fix, and enhancement update

Published Aug 6, 2026
·
Updated

Moderate: systemd security, bug fix, and enhancement update

Other sources

The systemd packages contain systemd, a system and service manager for Linux, compatible with the SysV and LSB init scripts. It provides aggressive parallelism capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, and keeps track of processes using Linux cgroups. In addition, it supports snapshotting and restoring of the system state, maintains mount and automount points, and implements an elaborate transactional dependency-based service control logic. It can also work as a drop-in replacement for sysvinit.Security Fix(es): systemd: systemd: Arbitrary code execution or Denial of Service via spurious IPC API call data (CVE-2026-29111) Bug Fix(es) and Enhancement(s): spec: systemd build fails due to rename of rhel-net-naming-sysattrs upstream [rhel-9.4.z] (JIRA:RHEL-150626) 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

93 affected componentsFixes available
Red Hat Red Hat Enterprise Linux for Power, little endian - Extended Life Cycle
Red Hat Red Hat Enterprise Linux for ARM 64 - 4 years of updates
Red Hat Red Hat Enterprise Linux for IBM z Systems - Extended Life Cycle
Red Hat Red Hat Enterprise Linux for IBM z Systems - 4 years of updates
Red Hat Red Hat Enterprise Linux for ARM 64 - Extended Life Cycle
Red Hat Red Hat Enterprise Linux for x86_64 - Update Services for SAP Solutions
Red Hat Red Hat Enterprise Linux Server - AUS
Red Hat Red Hat Enterprise Linux for x86_64 - Extended Life Cycle
Red Hat Red Hat Enterprise Linux Server for Power LE - Update Services for SAP Solutions
redhat/systemd<252-32.el9_4.11
252-32.el9_4.11
redhat/rhel-net-naming-sysattrs<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-boot-unsigned-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-container<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-container<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-container-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-container-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-debugsource<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-debugsource<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-devel<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-devel<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-journal-remote<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-journal-remote-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-journal-remote-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-libs<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-libs<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-libs-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-libs-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-oomd<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-oomd-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-oomd-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-pam<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-pam-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-pam-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-resolved<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-resolved-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-resolved-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-rpm-macros<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-standalone-sysusers-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-standalone-sysusers-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-standalone-tmpfiles-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-standalone-tmpfiles-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-udev<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-udev-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-udev-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-container<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-container-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-debugsource<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-devel<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-journal-remote<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-journal-remote-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-libs<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-libs-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-oomd<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-oomd-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-pam<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-pam-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-resolved<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-resolved-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-standalone-sysusers-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-standalone-tmpfiles-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-udev<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-udev-debuginfo<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-boot-unsigned-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-container<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-container-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-debugsource<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-devel<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-journal-remote<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-journal-remote-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-libs<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-libs-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-oomd<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-oomd-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-pam<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-pam-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-resolved<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-resolved-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-standalone-sysusers-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-standalone-tmpfiles-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-udev<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-udev-debuginfo<252-32.el9_4.11.aa
252-32.el9_4.11.aa
redhat/systemd-journal-remote<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-oomd<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-pam<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-resolved<252-32.el9_4.11
252-32.el9_4.11
redhat/systemd-udev<252-32.el9_4.11
252-32.el9_4.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/systemd to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  2. Upgrade

    Upgrade redhat/rhel-net-naming-sysattrs to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  3. Upgrade

    Upgrade redhat/systemd-boot-unsigned-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  4. Upgrade

    Upgrade redhat/systemd-container to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  5. Upgrade

    Upgrade redhat/systemd-container-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  6. Upgrade

    Upgrade redhat/systemd-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  7. Upgrade

    Upgrade redhat/systemd-debugsource to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  8. Upgrade

    Upgrade redhat/systemd-devel to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  9. Upgrade

    Upgrade redhat/systemd-journal-remote to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  10. Upgrade

    Upgrade redhat/systemd-journal-remote-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  11. Upgrade

    Upgrade redhat/systemd-libs to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  12. Upgrade

    Upgrade redhat/systemd-libs-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  13. Upgrade

    Upgrade redhat/systemd-oomd to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  14. Upgrade

    Upgrade redhat/systemd-oomd-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  15. Upgrade

    Upgrade redhat/systemd-pam to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  16. Upgrade

    Upgrade redhat/systemd-pam-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  17. Upgrade

    Upgrade redhat/systemd-resolved to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  18. Upgrade

    Upgrade redhat/systemd-resolved-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  19. Upgrade

    Upgrade redhat/systemd-rpm-macros to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  20. Upgrade

    Upgrade redhat/systemd-standalone-sysusers-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  21. Upgrade

    Upgrade redhat/systemd-standalone-tmpfiles-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  22. Upgrade

    Upgrade redhat/systemd-udev to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  23. Upgrade

    Upgrade redhat/systemd-udev-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11
  24. Upgrade

    Upgrade redhat/systemd to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  25. Upgrade

    Upgrade redhat/systemd-boot-unsigned-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  26. Upgrade

    Upgrade redhat/systemd-container to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  27. Upgrade

    Upgrade redhat/systemd-container-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  28. Upgrade

    Upgrade redhat/systemd-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  29. Upgrade

    Upgrade redhat/systemd-debugsource to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  30. Upgrade

    Upgrade redhat/systemd-devel to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  31. Upgrade

    Upgrade redhat/systemd-journal-remote to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  32. Upgrade

    Upgrade redhat/systemd-journal-remote-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  33. Upgrade

    Upgrade redhat/systemd-libs to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  34. Upgrade

    Upgrade redhat/systemd-libs-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  35. Upgrade

    Upgrade redhat/systemd-oomd to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  36. Upgrade

    Upgrade redhat/systemd-oomd-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  37. Upgrade

    Upgrade redhat/systemd-pam to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  38. Upgrade

    Upgrade redhat/systemd-pam-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  39. Upgrade

    Upgrade redhat/systemd-resolved to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  40. Upgrade

    Upgrade redhat/systemd-resolved-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  41. Upgrade

    Upgrade redhat/systemd-standalone-sysusers-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  42. Upgrade

    Upgrade redhat/systemd-standalone-tmpfiles-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  43. Upgrade

    Upgrade redhat/systemd-udev to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  44. Upgrade

    Upgrade redhat/systemd-udev-debuginfo to a version that resolves this vulnerability.

    Fixed in 252-32.el9_4.11.aa
  45. Upgrade

    Upgrade systemd to a version that resolves this vulnerability.

    Patch CVE-2026-29111
  46. Compensating control

    If systemd is impacted by the described RHEL build failure (rhel-9.4.z) due to upstream rename of rhel-net-naming-sysattrs, apply the update/advisory changes referenced by Red Hat article 11258 (JIRA:RHEL-150626) before building or deploying systemd.

Event History

Aug 6, 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:54 PM
Data Sourced
via Red Hat·02:54 PM
Severity
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-2026:51134?

The severity of RHSA-2026:51134 is classified as medium with a score of 4.

2

How do I fix RHSA-2026:51134?

To fix RHSA-2026:51134, update the systemd packages to the latest version provided by Red Hat.

3

What does RHSA-2026:51134 address?

RHSA-2026:51134 addresses security vulnerabilities, bug fixes, and enhancements within the systemd packages.

4

Which packages are affected by RHSA-2026:51134?

The affected packages include redhat/systemd, redhat/systemd-container, and their corresponding debuginfo and devel versions.

5

When was RHSA-2026:51134 published?

RHSA-2026:51134 was published on August 6, 2026.

Company

Resources

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