CVE-2026-43169

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

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

A fix is available — apply it.

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

drm/buddy: Prevent BUG_ON by validating rounded allocation

When DRM_BUDDY_CONTIGUOUS_ALLOCATION is set, the requested size is rounded up to the next power-of-two via roundup_pow_of_two(). Similarly, for non-contiguous allocations with large min_block_size, the size is aligned up via round_up(). Both operations can produce a rounded size that exceeds mm->size, which later triggers BUG_ON(order > mm->max_order).

Example scenarios:

  • 9G CONTIGUOUS allocation on 10G VRAM memory:
roundup_pow_of_two(9G) = 16G > 10G
  • 9G allocation with 8G min_block_size on 10G VRAM memory:
round_up(9G, 8G) = 16G > 10G

Fix this by checking the rounded size against mm->size. For non-contiguous or range allocations where size > mm->size is invalid, return -EINVAL immediately. For contiguous allocations without range restrictions, allow the request to fall through to the existing __alloc_contig_try_harder() fallback.

This ensures invalid user input returns an error or uses the fallback path instead of hitting BUG_ON.

v2: (Matt A)

  • Add Fixes, Cc stable, and Closes tags for context

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 PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 13, 2026

Advisory Details (4)

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

drm/buddy: Prevent BUG_ON by validating rounded allocation - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/buddy: Prevent BUG_ON by validating rounded allocation - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/buddy: Prevent BUG_ON by validating rounded allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6236c1cd9fdf433d39ed28b2491ccdfe7ae95061
generic

drm/buddy: Prevent BUG_ON by validating rounded allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5488a29596cdba93a60a79398dc9b69d5bdadf92

Patch Availability(13)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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 181 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43169?
CVE-2026-43169 is a medium vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/buddy: Prevent BUG_ON by validating rounded allocation When DRMBUDDYCONTIGUOUS_ALLOCATION is set, the requested size is rounded up to the next power-of-two via rounduppowof_two(). Similarly, for non-contiguous allocations with…
When was CVE-2026-43169 disclosed?
CVE-2026-43169 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43169 actively exploited?
CVE-2026-43169 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-43169?
CVE-2026-43169 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43169, 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-43169

Explore →

Is Your Infrastructure Affected by CVE-2026-43169?

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