CVE & CISA-KEV Catalog

CVE-2026-31598

MEDIUM
5.5
CVSS v3
NVD

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible deadlock between unlink and dio_end_io_write ocfs2_unlink takes orphan dir inode_lock first and then ip_alloc_sem, while in ocfs2_dio_end_io_write, it acquires these locks in reverse order. This creates an ABBA lock ordering violation on lock classes ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE] and ocfs2_file_ip_alloc_sem_key. Lock Chain #0 (orphan dir inode_lock -> ip_alloc_sem): ocfs2_unlink ocfs2_prepare_orphan_dir ocfs2_lookup_lock_orphan_dir inode_lock(orphan_dir_inode) <- lock A __ocfs2_prepare_orphan_dir ocfs2_prepare_dir_for_insert ocfs2_extend_dir ocfs2_expand_inline_dir down_write(&oi->ip_alloc_sem) <- Lock B Lock Chain #1 (ip_alloc_sem -> orphan dir inode_lock): ocfs2_dio_end_io_write down_write(&oi->ip_alloc_sem) <- Lock B ocfs2_del_inode_from_orphan() inode_lock(orphan_dir_inode) <- Lock A Deadlock Scenario: CPU0 (unlink) CPU1 (dio_end_io_write) ------ ------ inode_lock(orphan_dir_inode) down_write(ip_alloc_sem) down_write(ip_alloc_sem) inode_lock(orphan_dir_inode) Since ip_alloc_sem is to protect allocation changes, which is unrelated with operations in ocfs2_del_inode_from_orphan. So move ocfs2_del_inode_from_orphan out of ip_alloc_sem to fix the deadlock.

How to fix

Remediation Available
linuxDebian
Fixed in:5.10.259-1CVE-2026-31598
Fixed in:6.1.176-1CVE-2026-31598
Fixed in:6.12.85-1CVE-2026-31598
Fixed in:6.19.14-1CVE-2026-31598
linuxUbuntu
Fixed in:5.15.0-186.196USN-8575-1
Fixed in:6.8.0-136.136USN-8567-1
linux-awsUbuntu
Fixed in:5.15.0-1112.119USN-8575-2
Fixed in:6.8.0-1061.64USN-8595-2
linux-aws-5.15Ubuntu
Fixed in:5.15.0-1112.119~20.04.1USN-8575-2
linux-aws-6.8Ubuntu
Fixed in:6.8.0-1061.64~22.04.1USN-8595-3
linux-aws-fipsUbuntu
Fixed in:5.15.0-1112.119+fips1USN-8575-2
Fixed in:6.8.0-1061.64+fips1USN-8595-3
linux-azureUbuntu
Fixed in:5.15.0-1117.126USN-8575-3
Fixed in:6.8.0-1063.71USN-8606-1
linux-azure-5.15Ubuntu
Fixed in:5.15.0-1117.126~20.04.1USN-8620-1
linux-azure-6.8Ubuntu
Fixed in:6.8.0-1063.71~22.04.1USN-8606-1
linux-azure-fdeUbuntu
Fixed in:5.15.0-1117.126USN-8610-1
Fixed in:6.8.0-1062.69USN-8607-1
linux-azure-fde-5.15Ubuntu
Fixed in:5.15.0-1117.126~20.04.2USN-8620-1
linux-azure-fde-6.8Ubuntu
Fixed in:6.8.0-1062.69~22.04.1USN-8609-1
linux-azure-fipsUbuntu
Fixed in:5.15.0-1117.126+fips1USN-8620-2
Fixed in:6.8.0-1063.71+fips2USN-8608-1
linux-fipsUbuntu
Fixed in:5.15.0-186.196+fips1USN-8575-2
Fixed in:6.8.0-136.136+fips2USN-8574-2
linux-gcpUbuntu
Fixed in:5.15.0-1112.122USN-8575-1
Fixed in:6.8.0-1064.72USN-8567-1
linux-gcp-5.15Ubuntu
Fixed in:5.15.0-1112.122~20.04.1USN-8668-1
linux-gcp-6.8Ubuntu
Fixed in:6.8.0-1064.72~22.04.1USN-8567-1
linux-gcp-fipsUbuntu
Fixed in:5.15.0-1112.122+fips1USN-8575-1
Fixed in:6.8.0-1064.72+fips1USN-8574-1
linux-gkeUbuntu
Fixed in:5.15.0-1108.114USN-8575-1
Fixed in:6.8.0-1059.67USN-8567-1
linux-gkeopUbuntu
Fixed in:5.15.0-1095.103USN-8575-1
Fixed in:6.8.0-1046.50USN-8567-1
linux-hwe-5.15Ubuntu
Fixed in:5.15.0-186.196~20.04.1USN-8575-1
linux-hwe-6.8Ubuntu
Fixed in:6.8.0-136.136~22.04.1USN-8619-1
linux-hwe-7.0Ubuntu
Fixed in:7.0.0-28.28~24.04.1USN-8569-1
linux-ibmUbuntu
Fixed in:5.15.0-1106.110USN-8575-2
Fixed in:6.8.0-1061.62USN-8574-3
linux-ibm-5.15Ubuntu
Fixed in:5.15.0-1106.110~20.04.1USN-8597-1
linux-ibm-6.8Ubuntu
Fixed in:6.8.0-1061.62~22.04.1USN-8574-3
linux-image-5.15.0-1053-nvidia-tegra-igxUbuntu
Fixed in:5.15.0-1053.53USN-8576-2
linux-image-5.15.0-1053-nvidia-tegra-igx-rtUbuntu
Fixed in:5.15.0-1053.53USN-8576-2
linux-image-5.15.0-1064-nvidia-tegraUbuntu
Fixed in:5.15.0-1064.66~20.04.1USN-8576-1
Fixed in:5.15.0-1064.66USN-8576-2
linux-image-5.15.0-1064-nvidia-tegra-rtUbuntu
Fixed in:5.15.0-1064.66~20.04.1USN-8576-1
Fixed in:5.15.0-1064.66USN-8576-2

This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityNone
AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploit Intelligence

0.43%probability of exploitation in 30 days
36thpercentile

Low risk: more likely to be exploited than 36% of all known CVEs.

References

Related Vulnerabilities

Other CWE-667 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2019-10072High7.573%-Fix
CVE-2002-1850High7.517%-Fix
CVE-2009-2699High7.514%-Fix
CVE-2004-0174High7.512%--
CVE-2009-4272High7.511%--
CVE-2020-24606High8.65.2%-Fix

Common questions

How do I fix CVE-2026-31598?

Published advisories record a fix for 256 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.

Is CVE-2026-31598 being actively exploited?

Not that we know of. CVE-2026-31598 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.43% is the estimated probability that it will be exploited in the next 30 days. That is higher than 36% of all scored CVEs.

How severe is CVE-2026-31598?

CVE-2026-31598 has a CVSS v3 base score of 5.5, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-31598 affect?

Published advisories record a fix for linux (Debian), linux (Ubuntu), linux-aws (Ubuntu), linux-aws-5.15 (Ubuntu), and 252 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-31598
CVE-2026-31598 severity badge

Markdown

[![CVE-2026-31598](https://tridentstack.com/cve/badge/CVE-2026-31598.svg)](https://tridentstack.com/cve/CVE-2026-31598)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-31598"><img src="https://tridentstack.com/cve/badge/CVE-2026-31598.svg" alt="CVE-2026-31598"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-01.