CVE-2026-53043

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-24. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

ocfs2/dlm: validate qr_numregions in dlm_match_regions()

Patch series "ocfs2/dlm: fix two bugs in dlm_match_regions()".

In dlm_match_regions(), the qr_numregions field from a DLM_QUERY_REGION network message is used to drive loops over the qr_regions buffer without sufficient validation. This series fixes two issues:

  • Patch 1 adds a bounds check to reject messages where qr_numregions
exceeds O2NM_MAX_REGIONS. The o2net layer only validates message byte length; it does not constrain field values, so a crafted message can set qr_numregions up to 255 and trigger out-of-bounds reads past the 1024-byte qr_regions buffer.
  • Patch 2 fixes an off-by-one in the local-vs-remote comparison loop,
which uses '<=' instead of '<', reading one entry past the valid range even when qr_numregions is within bounds.

This patch (of 2):

The qr_numregions field from a DLM_QUERY_REGION network message is used directly as loop bounds in dlm_match_regions() without checking against O2NM_MAX_REGIONS. Since qr_regions is sized for at most O2NM_MAX_REGIONS (32) entries, a crafted message with qr_numregions > 32 causes out-of-bounds reads past the qr_regions buffer.

Add a bounds check for qr_numregions before entering the loops.

CVSS v3
9.1
EG Score
9.1(high)
EPSS
40.4%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

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

ocfs2/dlm: validate qr_numregions in dlm_match_regions() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2/dlm: validate qr_numregions in dlm_match_regions() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2/dlm: validate qr_numregions in dlm_match_regions() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2/dlm: validate qr_numregions in dlm_match_regions() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ab3fbb01bc6d79091bc375e5235d360cd9b78be
generic

ocfs2/dlm: validate qr_numregions in dlm_match_regions() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c6e8fc3c007319981647b410c29bb5775048551
generic

ocfs2/dlm: validate qr_numregions in dlm_match_regions() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2/dlm: validate qr_numregions in dlm_match_regions() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2/dlm: validate qr_numregions in dlm_match_regions() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f8b91275912cd428289c1fb424bebd7ff5302bd

Vendor Advisories for CVE-2026-53043(2)

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

Data Freshness Timeline

(refreshed 77× in last 7d / 89× 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-07 04:44 UTCEG score recompute
  2. 2026-07-07 04:43 UTCGHSA enrichment
  3. 2026-07-07 00:23 UTCEG score recompute
  4. 2026-07-07 00:23 UTCGHSA enrichment
  5. 2026-07-06 20:04 UTCEG score recompute
  6. 2026-07-06 20:04 UTCGHSA enrichment
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 15:42 UTCEG score recompute
  10. 2026-07-06 15:41 UTCGHSA enrichment
  11. 2026-07-06 11:21 UTCEG score recompute
  12. 2026-07-06 11:21 UTCGHSA enrichment
  13. 2026-07-06 06:16 UTCEG score recompute
  14. 2026-07-06 06:16 UTCGHSA enrichment
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-06 01:36 UTCEG score recompute
  18. 2026-07-06 01:36 UTCGHSA enrichment
  19. 2026-07-05 21:17 UTCEG score recompute
  20. 2026-07-05 21:17 UTCGHSA enrichment
  21. 2026-07-05 16:58 UTCEG score recompute
  22. 2026-07-05 16:58 UTCGHSA enrichment
  23. 2026-07-05 12:39 UTCEG score recompute
  24. 2026-07-05 12:39 UTCGHSA enrichment
  25. 2026-07-05 08:19 UTCEG score recompute
Show 64 more
  1. 2026-07-05 08:19 UTCGHSA enrichment
  2. 2026-07-05 03:58 UTCEG score recompute
  3. 2026-07-05 03:58 UTCGHSA enrichment
  4. 2026-07-05 02:31 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 23:27 UTCEG score recompute
  7. 2026-07-04 23:27 UTCGHSA enrichment
  8. 2026-07-04 19:07 UTCEG score recompute
  9. 2026-07-04 19:07 UTCGHSA enrichment
  10. 2026-07-04 14:46 UTCEG score recompute
  11. 2026-07-04 14:46 UTCGHSA enrichment
  12. 2026-07-04 10:26 UTCEG score recompute
  13. 2026-07-04 10:26 UTCGHSA enrichment
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 06:07 UTCEG score recompute
  16. 2026-07-04 06:07 UTCGHSA enrichment
  17. 2026-07-04 01:47 UTCEG score recompute
  18. 2026-07-04 01:47 UTCGHSA enrichment
  19. 2026-07-03 21:28 UTCEG score recompute
  20. 2026-07-03 21:28 UTCGHSA enrichment
  21. 2026-07-03 17:08 UTCEG score recompute
  22. 2026-07-03 17:08 UTCGHSA enrichment
  23. 2026-07-03 12:50 UTCEG score recompute
  24. 2026-07-03 12:49 UTCGHSA enrichment
  25. 2026-07-03 07:55 UTCEG score recompute
  26. 2026-07-03 07:55 UTCGHSA enrichment
  27. 2026-07-03 03:35 UTCEG score recompute
  28. 2026-07-03 03:35 UTCGHSA enrichment
  29. 2026-07-02 23:15 UTCEG score recompute
  30. 2026-07-02 23:14 UTCGHSA enrichment
  31. 2026-07-02 18:55 UTCEG score recompute
  32. 2026-07-02 18:55 UTCGHSA enrichment
  33. 2026-07-02 14:36 UTCEG score recompute
  34. 2026-07-02 14:36 UTCGHSA enrichment
  35. 2026-07-02 10:17 UTCEG score recompute
  36. 2026-07-02 10:17 UTCGHSA enrichment
  37. 2026-07-02 05:58 UTCEG score recompute
  38. 2026-07-02 05:58 UTCGHSA enrichment
  39. 2026-07-02 01:38 UTCEG score recompute
  40. 2026-07-02 01:38 UTCGHSA enrichment
  41. 2026-07-01 21:19 UTCEG score recompute
  42. 2026-07-01 21:19 UTCGHSA enrichment
  43. 2026-07-01 17:00 UTCEG score recompute
  44. 2026-07-01 17:00 UTCGHSA enrichment
  45. 2026-07-01 15:07 UTCEPSS rescore
  46. 2026-07-01 12:41 UTCEG score recompute
  47. 2026-07-01 12:41 UTCGHSA enrichment
  48. 2026-07-01 08:22 UTCEG score recompute
  49. 2026-07-01 08:22 UTCGHSA enrichment
  50. 2026-07-01 04:03 UTCEG score recompute▲ 9.10
  51. 2026-07-01 04:02 UTCGHSA enrichment
  52. 2026-06-30 23:22 UTCEPSS rescore
  53. 2026-06-29 14:06 UTCEPSS rescore
  54. 2026-06-29 14:06 UTCEPSS rescore
  55. 2026-06-28 14:07 UTCEPSS rescore
  56. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  57. 2026-06-28 04:56 UTCEPSS rescore
  58. 2026-06-28 04:56 UTCEPSS rescore
  59. 2026-06-27 23:10 UTCEG score recompute
  60. 2026-06-27 23:10 UTCGHSA enrichment
  61. 2026-06-27 03:08 UTCEPSS rescore
  62. 2026-06-25 13:49 UTCEPSS rescore
  63. 2026-06-24 18:18 UTCEG score recompute
  64. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53043?
CVE-2026-53043 is a critical vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2/dlm: validate qrnumregions in dlmmatch_regions() Patch series "ocfs2/dlm: fix two bugs in dlmmatchregions()". In dlmmatchregions(), the qrnumregions field from a DLMQUERY_REGION network message is used to drive loops over the…
When was CVE-2026-53043 disclosed?
CVE-2026-53043 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53043 actively exploited?
CVE-2026-53043 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53043?
CVE-2026-53043 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-53043?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53043, 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-53043

Explore →

Is Your Infrastructure Affected by CVE-2026-53043?

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

Start Free Scan →Browse All CVEs