Skip to main content
VulnerabilityPublished Updated

CVE-2026-46080: Linux kernel · ocfs2: split transactions in dio completion to avoid credit exhaustion

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ea5bb1d20da756e4f41a48dad42b2e7d6e73f71e : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in ea5bb1d20da756e4f41a48dad42b2e7d6e73f71e, d647c5b2fbf81560818dacade360abc8c00a9665, 886f97fa59d0bbfa9859fb1a66dd9e014b522d89 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c15471f79506830f80eca0e7fe09b8213953ab5f, < ea5bb1d20da756e4f41a48dad42b2e7d6e73f71e
Fixed in
  • ea5bb1d20da756e4f41a48dad42b2e7d6e73f71e
LinuxLinuxAffected
  • ≥ c15471f79506830f80eca0e7fe09b8213953ab5f, < d647c5b2fbf81560818dacade360abc8c00a9665
Fixed in
  • d647c5b2fbf81560818dacade360abc8c00a9665
LinuxLinuxAffected
  • ≥ c15471f79506830f80eca0e7fe09b8213953ab5f, < 886f97fa59d0bbfa9859fb1a66dd9e014b522d89
Fixed in
  • 886f97fa59d0bbfa9859fb1a66dd9e014b522d89
LinuxLinuxAffected
  • ≥ c15471f79506830f80eca0e7fe09b8213953ab5f, < 97c03c0e9f73a5049794b3c69ee60fb5e8b0ebd8
Fixed in
  • 97c03c0e9f73a5049794b3c69ee60fb5e8b0ebd8
LinuxLinuxAffected
  • ≥ c15471f79506830f80eca0e7fe09b8213953ab5f, < 91e05ac2336d00d5b99fc774be4bd50039084796
Fixed in
  • 91e05ac2336d00d5b99fc774be4bd50039084796
LinuxLinuxAffected
  • ≥ c15471f79506830f80eca0e7fe09b8213953ab5f, < 069c3fb310e9336cf48cfdf8748a32c29fd0193d
Fixed in
  • 069c3fb310e9336cf48cfdf8748a32c29fd0193d

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.

References

Community reviews

Loading reviews…