CVE-2026-46080

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
2.4%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (8)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

ocfs2: split transactions in dio completion to avoid credit exhaustion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea5bb1d20da756e4f41a48dad42b2e7d6e73f71e
generic

ocfs2: split transactions in dio completion to avoid credit exhaustion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d647c5b2fbf81560818dacade360abc8c00a9665
generic

ocfs2: split transactions in dio completion to avoid credit exhaustion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97c03c0e9f73a5049794b3c69ee60fb5e8b0ebd8
generic

ocfs2: split transactions in dio completion to avoid credit exhaustion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91e05ac2336d00d5b99fc774be4bd50039084796
generic

ocfs2: split transactions in dio completion to avoid credit exhaustion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/886f97fa59d0bbfa9859fb1a66dd9e014b522d89
generic

ocfs2: split transactions in dio completion to avoid credit exhaustion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3c636a3edca9c3f180b3079f94fe7e115730d9c6
generic

ocfs2: split transactions in dio completion to avoid credit exhaustion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e99bb19994246514d63e656492904176f9d5edd
generic

ocfs2: split transactions in dio completion to avoid credit exhaustion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/069c3fb310e9336cf48cfdf8748a32c29fd0193d

Vendor Advisories for CVE-2026-46080(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-11ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-11ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-11ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 101 total refreshes for this CVE.

  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 23:30 UTCEG score recompute
  5. 2026-07-11 23:30 UTCVendor advisory
  6. 2026-07-11 23:30 UTCGHSA enrichment
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-08 23:50 UTCEG score recompute
  10. 2026-07-08 23:50 UTCVendor advisory
  11. 2026-07-08 23:50 UTCGHSA enrichment
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-01 15:07 UTCEPSS rescore
  19. 2026-07-01 10:11 UTCEG score recompute
  20. 2026-07-01 10:11 UTCVendor advisory
  21. 2026-07-01 10:11 UTCGHSA enrichment
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-29 14:19 UTCEG score recompute
  24. 2026-06-29 14:19 UTCVendor advisory
  25. 2026-06-29 14:19 UTCGHSA enrichment
Show 75 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 06:43 UTCEG score recompute
  5. 2026-06-28 06:43 UTCVendor advisory
  6. 2026-06-28 06:42 UTCGHSA enrichment
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-27 05:49 UTCEG score recompute
  10. 2026-06-27 05:49 UTCVendor advisory
  11. 2026-06-27 05:49 UTCGHSA enrichment
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-26 02:27 UTCEG score recompute
  14. 2026-06-26 02:27 UTCVendor advisory
  15. 2026-06-26 02:27 UTCGHSA enrichment
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 00:59 UTCEG score recompute▲ 5.50
  18. 2026-06-25 00:59 UTCVendor advisory
  19. 2026-06-25 00:59 UTCGHSA enrichment
  20. 2026-06-24 18:02 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  21. 2026-06-24 14:05 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-23 21:33 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
  26. 2026-06-21 14:56 UTCEPSS rescore
  27. 2026-06-21 14:56 UTCEPSS rescore
  28. 2026-06-21 01:59 UTCEPSS rescore
  29. 2026-06-21 01:59 UTCEPSS rescore
  30. 2026-06-19 19:26 UTCEPSS rescore
  31. 2026-06-19 19:26 UTCEPSS rescore
  32. 2026-06-18 17:52 UTCEPSS rescore
  33. 2026-06-18 17:52 UTCEPSS rescore
  34. 2026-06-17 17:53 UTCEPSS rescore
  35. 2026-06-16 17:52 UTCEPSS rescore
  36. 2026-06-16 09:39 UTCVendor advisory
  37. 2026-06-16 09:39 UTCGHSA enrichment
  38. 2026-06-15 17:49 UTCEPSS rescore
  39. 2026-06-14 23:28 UTCMITRE cvelistV5
  40. 2026-06-13 23:00 UTCEPSS rescore
  41. 2026-06-13 07:42 UTCVendor advisory
  42. 2026-06-13 07:42 UTCGHSA enrichment
  43. 2026-06-12 23:12 UTCEPSS rescore
  44. 2026-06-12 23:12 UTCEPSS rescore
  45. 2026-06-11 14:00 UTCEPSS rescore
  46. 2026-06-10 22:18 UTCEPSS rescore
  47. 2026-06-10 13:22 UTCEPSS rescore
  48. 2026-06-10 13:22 UTCEPSS rescore
  49. 2026-06-10 06:05 UTCGHSA enrichment
  50. 2026-06-08 14:17 UTCEPSS rescore
  51. 2026-06-08 14:17 UTCEPSS rescore
  52. 2026-06-07 15:25 UTCEPSS rescore
  53. 2026-06-07 15:25 UTCEPSS rescore
  54. 2026-06-07 04:34 UTCGHSA enrichment
  55. 2026-06-06 13:47 UTCEPSS rescore
  56. 2026-06-06 13:47 UTCEPSS rescore
  57. 2026-06-05 22:47 UTCEPSS rescore
  58. 2026-06-05 06:10 UTCEPSS rescore
  59. 2026-06-05 06:10 UTCEPSS rescore
  60. 2026-06-04 13:12 UTCEPSS rescore
  61. 2026-06-04 13:12 UTCEPSS rescore
  62. 2026-06-04 03:03 UTCGHSA enrichment
  63. 2026-06-02 20:13 UTCEPSS rescore
  64. 2026-06-01 13:52 UTCEPSS rescore
  65. 2026-06-01 13:52 UTCEPSS rescore
  66. 2026-06-01 01:31 UTCEG score recompute
  67. 2026-06-01 01:31 UTCGHSA enrichment
  68. 2026-05-31 22:30 UTCEPSS rescore
  69. 2026-05-31 22:30 UTCEPSS rescore
  70. 2026-05-31 00:16 UTCEPSS rescore
  71. 2026-05-31 00:16 UTCEPSS rescore
  72. 2026-05-29 13:44 UTCEPSS rescore
  73. 2026-05-29 13:44 UTCEPSS rescore
  74. 2026-05-28 13:44 UTCEPSS rescore
  75. 2026-05-28 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-46080?
CVE-2026-46080 is a medium vulnerability published on May 27, 2026. 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: ocfs2dioendiowrite ocfs2markextent_written ocfs2changeextent_flag…
When was CVE-2026-46080 disclosed?
CVE-2026-46080 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46080 actively exploited?
CVE-2026-46080 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46080?
CVE-2026-46080 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46080?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46080, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46080

Explore →

Is Your Infrastructure Affected by CVE-2026-46080?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs