RHSA-2024:6345 — OpenSSL security update

Critical Issued: Oct 15, 2024 · CVSS: 8.1 · Affects: RHEL 8, RHEL 9

Synopsis

An update for openssl is now available for Red Hat Enterprise Linux 8 and Red Hat Enterprise Linux 9. This update includes security fixes for CVE-2024-6345, addressing a critical buffer overflow vulnerability in the OpenSSL TLS handshake.

Affected Packages

openssl-3.0.7-27.el9.x86_64 openssl-libs-3.0.7-27.el9.x86_64 openssl-devel-3.0.7-27.el9.x86_64

Affected Systems (from Insights)

8 of 30 registered systems are affected. View in Vulnerability →

AI-assisted responses Powered by Red Hat AI

Session Context (auto-loaded)

⚠ RHSA-2024:6345 📦 openssl-3.0.7-27 🖥 8 affected systems ⬇ Downloaded RPM

Red Hat Support Agent

Hi Priya. I can see you've been reviewing RHSA-2024:6345 and downloaded the patched OpenSSL RPM. How can I help?

Dependency conflict when applying openssl-3.0.7-27 on systems with custom kernel module.

Red Hat Support Agent

I found two related KB articles for resolving dependency conflicts with custom kernel modules during OpenSSL updates:

When a custom kernel module links against libssl or libcrypto, updating OpenSSL can fail with an unresolved symbol error. To resolve:

1. Run rpm -qa --last | grep kernel to identify the custom module
2. Temporarily remove the custom module: modprobe -r custom_module
3. Apply the OpenSSL update: dnf update openssl
4. Rebuild the custom module against the new OpenSSL headers
5. Reload: modprobe custom_module

View full article on access.redhat.com →

Compatibility matrix for custom kernel modules compiled against OpenSSL versions 3.0.1 through 3.0.7. Your systems running kernel 5.14.0-362 should use the --rebuild-module flag during the update.

View full article on access.redhat.com →

The first article matches your scenario — custom kernel module with OpenSSL dependency conflict. Would you like me to walk you through the steps, or would you prefer to open a support case with this context pre-filled?

📋 Open a support case

Vision Screen 4 of 5 — Conversational Support Agent · Beat 3: Support with context