CVE-2026-46224

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-05-28.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

A fix is available — apply it.

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

drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure

When drm_gpuvm_resv_object_alloc() fails, the pre-allocated storage bo is not freed. Add xe_bo_free(storage) before returning the error.

xe_dma_buf_init_obj() calls xe_bo_init_locked(), which frees the bo on error. Therefore, xe_dma_buf_init_obj() must also free the bo on its own error paths. Otherwise, since xe_gem_prime_import() cannot distinguish whether the failure originated from xe_dma_buf_init_obj() or from xe_bo_init_locked(), it cannot safely decide whether the bo should be freed.

Add comments documenting the ownership semantics: on success, ownership of storage is transferred to the returned drm_gem_object; on failure, storage is freed before returning.

v2: Add comments to explain the free logic.

(cherry picked from commit 78a6c5f899f22338bbf48b44fb8950409c5a69b9)

CVSS v3
—
EG Score
5.5(low)
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 PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 14, 2026

References (3)

Vendor Advisories for CVE-2026-46224(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (135 versions)7.0.9-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

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 4× in last 7d / 66× 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 191 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2026-46224?
CVE-2026-46224 is a medium vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix bo leak in xedmabufinitobj() on allocation failure When drmgpuvmresvobjectalloc() fails, the pre-allocated storage bo is not freed. Add xebofree(storage) before returning the error. xedmabufinitobj() calls…
When was CVE-2026-46224 disclosed?
CVE-2026-46224 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46224 actively exploited?
CVE-2026-46224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.1% of all scored CVEs.
How do I remediate CVE-2026-46224?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46224, 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-46224

Explore →

Is Your Infrastructure Affected by CVE-2026-46224?

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

Start Free Scan →Browse All CVEs