kpatch-patch-4_18_0-553_109_1, kpatch-patch-4_18_0-553_40_1, kpatch-patch-4_18_0-553_53_1, kpatch-patch-4_18_0-553_72_1, and kpatch-patch-4_18_0-553_85_1 security update — RHSA-2026:15976
Red Hat · Red Hat · RHSA-2026:15976
ID
RHSA-2026:15976
RHSA-2026:15976
Date
Updated
Source
Red Hat
Red Hat
Vendor
Red Hat
Red Hat
Threat
high
high
Summary
RHSA-2026:15976 is a security advisory from Red Hat. kpatch-patch-4_18_0-553_109_1, kpatch-patch-4_18_0-553_40_1, kpatch-patch-4_18_0-553_53_1, kpatch-patch-4_18_0-553_72_1, and kpatch-patch-4_18_0-553_85_1 security update Vendor: Red Hat. Reported severity or threat: high. Source updated on 2026-08-04.
Timeline
- Published by source
- 2026-05-11
- Last source activity
- 2026-08-04
- Time from publication to latest source activity
- 85 days
Risk context
- Reported severity or threat level: high.
- Review exposure for the affected product or family: Red Hat Enterprise Linux for x86_64 | Red Hat Enterprise Linux for x86_64 - Extended Life Cycle | Red Hat Enterprise Linux for Power, little endian | Red Hat Enterprise Linux for Power, little endian - Extended Life Cycle.
Product
Red Hat Enterprise Linux for x86_64 | Red Hat Enterprise Linux for x86_64 - Extended Life Cycle | Red Hat Enterprise Linux for Power, little endian | Red Hat Enterprise Linux for Power, little endian - Extended Life Cycle
What to do
General, cautious steps (verify details in the official source):
- Prioritize patching or mitigation immediately (treat as actively risky).
- Identify affected product versions in your inventory and verify whether you are impacted.
- Apply vendor patches/updates or recommended mitigations as soon as available.
- Read the official advisory for exact affected versions and remediation steps.
Official advisory
Evidence and provenance
- Canonical advisory ID
- RHSA-2026:15976
- Source
- Red Hat
- Vendor
- Red Hat
- Published by source
- 2026-05-11
- Last source activity
- 2026-08-04
- Additional identifiers
- 15976
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.