Red Hat Extends CVE-2026-98260 Kernel Fixes Across RHEL 9

P1 — VALIDATE AND UPDATEHigh · 7.8 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Red Hat added RHSA-2026:83775 for RHEL 9.6 EUS and RHSA-2026:83797 for RHEL 9.4 SAP E4S to the existing CVE-2026-98260 kernel notice. Match entitled systems to the exact advisory, install the complete architecture-specific package set, follow the advisory restart guidance, validate the running kernel and dependent workloads, and retain evidence.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory RHEL 9.2 SAP E4S, 9.4 SAP E4S, and 9.6 EUS systems; match each host to the entitled advisory and architecture; preserve operational evidence; install the complete package set; follow the advisory restart indication; validate the running kernel and workloads; and document exceptions.

Open the authoritative advisory

Last verified: 2026-10-17 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeRHEL 9.2 SAP E4S, RHEL 9.4 SAP E4S, and RHEL 9.6 EUS kernel package families listed in RHSA-2026:83738, RHSA-2026:83797, and RHSA-2026:83775
AdvisoryRHSA-2026:83738 / RHSA-2026:83775 / RHSA-2026:83797
CVECVE-2026-98260
Authoritative release date2026-10-16 15:07:45 UTC; initial RHSA-2026:83738 publication
Authority revision date2026-10-16 23:04:23 UTC; current Red Hat CSAF revision after adding RHSA-2026:83775 and RHSA-2026:83797
Affected versionsEntitled deployments matched to the three Red Hat advisories and their listed AppStream, BaseOS, CodeReady Builder, Real Time, or NFV product branches; the CSAF documents list fixed package sets rather than a general affected-version range.
Fixed versionthe complete advisory-matched package set for the deployed architecture: kernel 5.14.0-284.198.1.el9_2 for RHEL 9.2 SAP E4S, 5.14.0-427.156.1.el9_4 for RHEL 9.4 SAP E4S, or 5.14.0-570.149.1.el9_6 for RHEL 9.6 EUS
CVSS base score7.8 (CVSS v3.1)
CVSS severityHigh
Exploitation statusNot stated by Red Hat; no exploitation claim is inferred.

What Changed

Red Hat added RHEL 9.6 Extended Update Support and RHEL 9.4 Update Services for SAP Solutions package families to the previously published RHEL 9.2 SAP E4S coverage for the same kernel use-after-free. The newer CSAF documents provide branch-specific fixed packages and do not state that exploitation has occurred.

What To Validate Now

  1. Inventory. Locate the three covered RHEL 9 branches, record architecture, enabled repositories, installed and running kernels, workload role, maintenance owner, clustering, and recovery dependencies.
  2. Establish applicability. Match each host to RHSA-2026:83738, RHSA-2026:83797, or RHSA-2026:83775 and the exact entitled product branch. Do not apply one branch's package statement to another stream.
  3. Remediate. Install the complete advisory package set for the host architecture. RHSA-2026:83738 marks a machine restart as required; the newer CSAF documents do not mark a restart as required, so follow the current advisory and local kernel activation policy rather than generalizing across branches.
  4. Validate. Confirm installed packages and the effective running kernel, verify repository alignment, test application, SAP, clustering, Real Time or NFV functions as applicable, review boot and kernel logs, and confirm rollback readiness.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

The three advisories share a CVE but cover different entitled branches and package sets. Preserve a known-good boot path and coordinate any restart with service owners. Do not infer compromise from severity or assume that installing packages alone activates a new kernel.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.