Skip to content
VulniPulse
High7.0Red Hat Linux

High [CVE-2026-72183] Fix LANDLOCK_SCOPE_SIGNAL bypass on the SIGIO path

This high-severity Red Hat Linux advisory covers CVE-2026-72183 affecting Red Hat Enterprise Linux 9, Red Hat package: kernel-rt.

CVE-2026-72183 Published Aug 15, 2026Updated by vendor Aug 15, 2026
Affected products & platforms
Red Hat LinuxLinux Kernel
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A flaw was found in the Linux kernel's Landlock security module. A sandboxed process can bypass the intended signal isolation provided by LANDLOCK_SCOPE_SIGNAL.

By manipulating file descriptors with specific `fcntl` calls and asynchronous I/O (SIGIO) delivery, a local attacker can send signals, such as a kill signal, to processes outside its Landlock domain. This could lead to a denial of service or unauthorized process termination of critical system processes.

Red Hat severity: Important — CVSS 7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-501.

Affected Red Hat products: Red Hat Enterprise Linux 9. Red Hat does not currently list a fixing RHSA for this CVE.

Affected products named by the advisory: Red Hat package: kernel-rt.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.