Skip to content
Systems

CVE-2026-72183

8.4
High
EPSS 0.17%Patch availableAug 17, 2026

Linux kernel Landlock SIGIO path bypass lets sandboxed processes signal external processes

common questions

Is CVE-2026-72183 being exploited?

Not confirmed. CVE-2026-72183 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.17% probability of exploitation in the next 30 days.

How severe is CVE-2026-72183?

CVE-2026-72183 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-72183?

Yes. A fix has been recorded for CVE-2026-72183. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72183 affect?

CVE-2026-72183 affects Linux kernel (Landlock enabled), Containers and sandboxed apps using Landlock, Distributions shipping patched kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72183?

Apply Linux kernel updates and reboot or restart affected services; validate Landlock usage

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (Landlock enabled)Containers and sandboxed apps using LandlockDistributions shipping patched kernels
impact

Sandboxed process can use SIGIO to deliver signals (e.g., SIGKILL) to processes outside its Landlock domain, enabling process termination, DoS, or sandbox escape escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 332facfa80751b80006c2f95b13c6d208ab0aee1 and < 7a92e9fd1d496a610b40e0c4253fd54e7496f5ab
  • affected>= 18eb75f3af40be1f0fc2025d4ff821711222a2fd and < 1f18aac2637220b5847d073447498e81ddca10b2
  • affected>= 18eb75f3af40be1f0fc2025d4ff821711222a2fd and < 04916f7dc6d37cd478b06c86398c34a6963ac8c9
  • affected>= 18eb75f3af40be1f0fc2025d4ff821711222a2fd and < 4b80320ca7ed03d6e683f95b6066565dc97b9f92
  • affected6861348d863c0eaa4af67492d640a9644a829c59
  • affected0906a9685d7057aea982e970da3e1cf3e5aca68b
  • affected>= 6.12.24 and < 6.12.101
  • affected>= 6.13.12 and < 6.14
  • affected>= 6.14.3 and < 6.15
  • affected6.15
vendor says fixed in< 6.15, >= 6.12.101 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free