LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects OCFS2 filesystem handling during direct I/O write completion. The kernel fix prevents transaction credit exhaustion and improves crash consistency around orphan inode cleanup. Business impact is most relevant where OCFS2 supports clustered or shared storage. No severity score or active exploitation evidence is provided in the source bundle.

Executive priority

Treat as targeted infrastructure maintenance unless OCFS2 underpins business-critical clustered storage. Because severity and exploitability are not scored, prioritize confirmation of OCFS2 usage first, then patch affected systems through normal kernel update channels.

Technical view

The flaw is in ocfs2_dio_end_io_write(). Large extent updates during DIO completion can exceed JBD2 transaction credit limits. The fix batches extent handling across transactions and delays orphan-list removal until extent tree updates complete, reducing the risk of stale blocks beyond EOF after a crash.

Likely exposure

Exposure appears limited to Linux systems using OCFS2 on affected kernel versions or branches, especially with direct I/O write workloads. Systems not using OCFS2 are unlikely to be exposed based on the provided description.

Exploitation context

The source bundle does not report public exploitation, weaponized exploit code, or CISA KEV listing. The described condition appears tied to filesystem operation and crash-consistency behavior, not a broadly remote attack path.

Researcher notes

Evidence is limited to the CVE record and kernel stable references. The core risk is transaction credit exhaustion during OCFS2 direct I/O extent updates, with crash-consistency implications. No CVSS, CWE, exploit status, or distro-specific fixed packages are included.

Mitigation direction

  • Upgrade to a vendor kernel containing the referenced stable OCFS2 fixes.
  • Prioritize systems using OCFS2 for clustered or critical shared storage.
  • Check distribution advisories for exact fixed package versions.
  • Reduce unnecessary OCFS2 direct I/O exposure until patched, where operationally feasible.

Validation and detection

  • Inventory Linux hosts using OCFS2 filesystems.
  • Compare running kernel versions against vendor advisories and referenced stable commits.
  • Review kernel logs for JBD2 credit exhaustion warnings involving OCFS2.
  • Confirm patched kernels are deployed and booted, not merely installed.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46080 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc15471f79506830f80eca0e7fe09b8213953ab5f, c15471f79506830f80eca0e7fe09b8213953ab5f, c15471f79506830f80eca0e7fe09b8213953ab5f, c15471f79506830f80eca0e7fe09b8213953ab5f, c15471f79506830f80eca0e7fe09b8213953ab5f, c15471f79506830f80eca0e7fe09b8213953ab5f, c15471f79506830f80eca0e7fe09b8213953ab5f, c15471f79506830f80eca0e7fe09b8213953ab5funaffected
LinuxLinux4.6, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.