CVE-2026-53043

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-24. the CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Sep 7, 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/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/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/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/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/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/1f8b91275912cd428289c1fb424bebd7ff5302bd
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/d3d5efade0c79dac1cac98c0cb1115432f804439

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.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-31ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1056.57~22.04.2) @ jammy2026-08-31ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-31ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-31ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-31ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-31ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-31ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-31ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-31ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-31ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-31ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-31ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-31ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-31ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-31ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-31ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.257.241) @ bionic2026-08-31ubuntu
ubuntulinux-virtual (3.13.0.217.227) @ trusty2026-08-31ubuntu
ubuntulinux-tools-gke (4.15.0.1189.206~16.04.1) @ xenial2026-08-31ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-31ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-31ubuntu
ubuntulinux-tools-azure-edge (4.15.0.1206.221~16.04.1) @ xenial2026-08-31ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-31ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-31ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-31ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-31ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-31ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-31ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-31ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-31ubuntu

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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(25)

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 5× in last 7d / 148× 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 491 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 5, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 57.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53043?
CVE-2026-53043 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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