CVE-2024-26369

What it actually does

The flaw in the HistoryQosPolicy component triggers a SIGABRT signal abort when the process receives DataWriter data, terminating the affected application.

Why it matters to the business

Service disruptions from unexpected process crashes can interrupt dependent applications on AlmaLinux systems, increasing downtime and operational recovery costs despite low exploit likelihood.

How an attack unfolds

An attacker sends specially crafted data to a DataWriter instance in an affected FastDDS deployment; the HistoryQosPolicy mishandles the input and forces an immediate SIGABRT, crashing the process.

How to fix it

Upgrade libnotify to 0.7.7-6.el8 and libnotify-devel to 0.7.7-6.el8 on AlmaLinux 8; rebuild and restart any services using the library after applying the update.

How to confirm the fix worked

Confirm package versions match the fixed releases using package manager queries and test data ingestion flows to verify no SIGABRT occurs on receipt of DataWriter messages.

Typical attack path

1. Identify exposed FastDDS endpoints accepting DataWriter traffic
2. Craft and transmit malformed data payloads targeting HistoryQosPolicy handling
3. Trigger SIGABRT to cause denial of service

How to detect it

Review application and system logs for sudden SIGABRT entries or process terminations correlated with incoming DataWriter traffic; no widespread exploitation has been observed.

What your security team should do

• Apply the specified package updates immediately on all AlmaLinux 8 systems running the affected versions
• Monitor EPSS and exploit maturity indicators for any future increase in risk
• Review downstream dependents for similar exposure and schedule upgrades