CVE-2026-46080

ocfs2: split transactions in dio completion to avoid credit exhaustion

MEDIUM
5.5
CVSS Score
Published: May 27, 2026 at 12:58 PM UTC
Updated: June 27, 2026 at 11:41 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: split transactions in dio completion to avoid credit exhaustion During ocfs2 dio operations, JBD2 may report warnings via following call trace: ocfs2_dio_end_io_write ocfs2_mark_extent_written ocfs2_change_extent_flag ocfs2_split_extent ocfs2_try_to_merge_extent ocfs2_extend_rotate_transaction ocfs2_extend_trans jbd2__journal_restart start_this_handle output: JBD2: kworker/6:2 wants too many credits credits:5450 rsv_credits:0 max:5449 To prevent exceeding the credits limit, modify ocfs2_dio_end_io_write() to handle extents in a batch of transaction. Additionally, relocate ocfs2_del_inode_from_orphan(). The orphan inode should only be removed from the orphan list after the extent tree update is complete. This ensures that if a crash occurs in the middle of extent tree updates, we won't leave stale blocks beyond EOF. This patch also changes the logic for updating the inode size and removing orphan, making it similar to ext4_dio_write_end_io(). Both operations are performed only when everything looks good. Finally, thanks to Jans and Joseph for providing the bug fix prototype and suggestions.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.6 ≤ v < 5.10.2584.6 ≤ v < 5.15.2094.6 ≤ v < 6.1.1754.6 ≤ v < 6.12.864.6 ≤ v < 6.18.274.6 ≤ v < 6.6.1404.6 ≤ v < 7.0.44.6 ≤ v < 7.15.11 ≤ v < 5.15.2095.16 ≤ v < 6.1.1756.13 ≤ v < 6.18.276.19 ≤ v < 7.0.46.2 ≤ v < 6.6.1406.7 ≤ v < 6.12.864.6c15471f79506830f80eca0e7fe09b8213953ab5f
Vendor states this is fixed in 1e99bb19994246514d63e656492904176f9d5edd (fixed)
Vendor states this is fixed in 3c636a3edca9c3f180b3079f94fe7e115730d9c6 (fixed)
Vendor states this is fixed in 69c3fb310e9336cf48cfdf8748a32c29fd193d (fixed)
Vendor states this is fixed in 886f97fa59d0bbfa9859fb1a66dd9e014b522d89 (fixed)
Vendor states this is fixed in 91e05ac2336d00d5b99fc774be4bd50039084796 (fixed)
Vendor states this is fixed in 97c03c0e9f73a5049794b3c69ee60fb5e8b0ebd8 (fixed)
Vendor states this is fixed in d647c5b2fbf81560818dacade360abc8c00a9665 (fixed)
Vendor states this is fixed in ea5bb1d20da756e4f41a48dad42b2e7d6e73f71e (fixed)
Vendor states this is fixed in 4.6 (unaffected)
Vendor states this is fixed in 5.10.258 (unaffected)
Vendor states this is fixed in 5.15.209 (unaffected)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.86 (unaffected)
Vendor states this is fixed in 6.18.27 (unaffected)
Vendor states this is fixed in 6.6.140 (unaffected)
Vendor states this is fixed in 7.0.4 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusUNDERGOING ANALYSIS
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card