CVE-2026-46061

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
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:

jbd2: fix deadlock in jbd2_journal_cancel_revoke()

Commit f76d4c28a46a ("fs/jbd2: use sleeping version of __find_get_block()") changed jbd2_journal_cancel_revoke() to use __find_get_block_nonatomic() which holds the folio lock instead of i_private_lock. This breaks the lock ordering (folio -> buffer) and causes an ABBA deadlock when the filesystem blocksize < pagesize:

T1 T2 ext4_mkdir() ext4_init_new_dir() ext4_append() ext4_getblk() lock_buffer() <- A sync_blockdev() blkdev_writepages() writeback_iter() writeback_get_folio() folio_lock() <- B ext4_journal_get_create_access() jbd2_journal_cancel_revoke() __find_get_block_nonatomic() folio_lock() <- B block_write_full_folio() lock_buffer() <- A

This can occasionally cause generic/013 to hang.

Fix by only calling __find_get_block_nonatomic() when the passed buffer_head doesn't belong to the bdev, which is the only case that we need to look up its bdev alias. Otherwise, the lookup is redundant since the found buffer_head is equal to the one we passed in.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.7%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (4)

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

jbd2: fix deadlock in jbd2_journal_cancel_revoke() - kernel/git/stable/linux.git - Linux kernel stable tree

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

jbd2: fix deadlock in jbd2_journal_cancel_revoke() - kernel/git/stable/linux.git - Linux kernel stable tree

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

jbd2: fix deadlock in jbd2_journal_cancel_revoke() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/981fcc5674e67158d24d23e841523eccba19d0e7
generic

jbd2: fix deadlock in jbd2_journal_cancel_revoke() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b2fee890250ab647a601124471a334bb01a0790

Vendor Advisories for CVE-2026-46061(1)

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

Patch Availability(4)

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 35× 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.

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

Frequently asked(5)

What is CVE-2026-46061?
CVE-2026-46061 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: jbd2: fix deadlock in jbd2journalcancel_revoke() Commit f76d4c28a46a ("fs/jbd2: use sleeping version of findgetblock()") changed jbd2journalcancel_revoke() to use findgetblock_nonatomic() which holds the folio lock instead of…
When was CVE-2026-46061 disclosed?
CVE-2026-46061 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46061 actively exploited?
CVE-2026-46061 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46061?
CVE-2026-46061 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46061?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46061, 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-46061

Explore →

Is Your Infrastructure Affected by CVE-2026-46061?

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