CVE-2026-80845
Description
A flaw was found in the Linux kernel's xfrm (IPSec framework) component. A lock inversion vulnerability exists within the nat_keepalive_work() function. This flaw can lead to an AB-BA deadlock when a Network Address Translation (NAT) keepalive worker races with Security Association (SA) deletion. The deadlock can cause the system to become unresponsive, resulting in a Denial of Service (DoS).
Statement
This vulnerability is evaluated as having a Low impact for Red Hat Enterprise Linux because triggering the lock inversion requires an active IPsec configuration utilizing NAT keepalive alongside concurrent security association removal. In standard environments, managing IPsec states requires elevated network administrative privileges, significantly constraining potential attack vectors. Consequently, unprivileged users cannot easily induce this deadlock to cause a system denial of service.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart
Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.