CVE-2026-43302

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. 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

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:

drm/v3d: Set DMA segment size to avoid debug warnings

When using V3D rendering with CONFIG_DMA_API_DEBUG enabled, the kernel occasionally reports a segment size mismatch. This is because 'max_seg_size' is not set. The kernel defaults to 64K. setting 'max_seg_size' to the maximum will prevent 'debug_dma_map_sg()' from complaining about the over-mapping of the V3D segment length.

DMA-API: v3d 1002000000.v3d: mapping sg segment longer than device claims to support [len=8290304] [max=65536] WARNING: CPU: 0 PID: 493 at kernel/dma/debug.c:1179 debug_dma_map_sg+0x330/0x388 CPU: 0 UID: 0 PID: 493 Comm: Xorg Not tainted 6.12.53-yocto-standard #1 Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT) pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : debug_dma_map_sg+0x330/0x388 lr : debug_dma_map_sg+0x330/0x388 sp : ffff8000829a3ac0 x29: ffff8000829a3ac0 x28: 0000000000000001 x27: ffff8000813fe000 x26: ffffc1ffc0000000 x25: ffff00010fdeb760 x24: 0000000000000000 x23: ffff8000816a9bf0 x22: 0000000000000001 x21: 0000000000000002 x20: 0000000000000002 x19: ffff00010185e810 x18: ffffffffffffffff x17: 69766564206e6168 x16: 74207265676e6f6c x15: 20746e656d676573 x14: 20677320676e6970 x13: 5d34303334393134 x12: 0000000000000000 x11: 00000000000000c0 x10: 00000000000009c0 x9 : ffff8000800e0b7c x8 : ffff00010a315ca0 x7 : ffff8000816a5110 x6 : 0000000000000001 x5 : 000000000000002b x4 : 0000000000000002 x3 : 0000000000000008 x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00010a315280 Call trace: debug_dma_map_sg+0x330/0x388 __dma_map_sg_attrs+0xc0/0x278 dma_map_sgtable+0x30/0x58 drm_gem_shmem_get_pages_sgt+0xb4/0x140 v3d_bo_create_finish+0x28/0x130 [v3d] v3d_create_bo_ioctl+0x54/0x180 [v3d] drm_ioctl_kernel+0xc8/0x140 drm_ioctl+0x2d4/0x4d8

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
2.4%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 15, 2026

Advisory Details (7)

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

drm/v3d: Set DMA segment size to avoid debug warnings - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/v3d: Set DMA segment size to avoid debug warnings - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/v3d: Set DMA segment size to avoid debug warnings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9eb018828b1b30dfba689c060735c50fc5b9f704
generic

drm/v3d: Set DMA segment size to avoid debug warnings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2663ef70c6123b2232190f917275e5c3175f97d0
generic

drm/v3d: Set DMA segment size to avoid debug warnings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/225023e3619b81af6d8d0e680503fc2d68633023
generic

drm/v3d: Set DMA segment size to avoid debug warnings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14d0d6c8b4504a60cfeea74775ab2e0164019e65
generic

drm/v3d: Set DMA segment size to avoid debug warnings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0290934d30abe7c88e18140fd5184c3f386b1e44

Vendor Advisories for CVE-2026-43302(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 44× 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-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:06 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 05:10 UTCEG score recompute
  14. 2026-06-28 05:10 UTCGHSA enrichment
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-26 21:36 UTCEG score recompute
  18. 2026-06-26 21:36 UTCGHSA enrichment
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:05 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-19 19:25 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-17 17:53 UTCEPSS rescore
  7. 2026-06-17 02:03 UTCEG score recompute
  8. 2026-06-17 02:02 UTCGHSA enrichment
  9. 2026-06-16 17:52 UTCEPSS rescore
  10. 2026-06-15 17:49 UTCEPSS rescore
  11. 2026-06-15 04:38 UTCEG score recompute
  12. 2026-06-15 04:38 UTCGHSA enrichment
  13. 2026-06-14 03:01 UTCEG score recompute
  14. 2026-06-14 03:01 UTCGHSA enrichment
  15. 2026-06-13 23:00 UTCEPSS rescore
  16. 2026-06-12 23:12 UTCEPSS rescore
  17. 2026-06-12 23:12 UTCEPSS rescore
  18. 2026-06-12 02:11 UTCEG score recompute
  19. 2026-06-12 02:11 UTCGHSA enrichment
  20. 2026-06-11 14:00 UTCEPSS rescore
  21. 2026-06-11 00:35 UTCEG score recompute
  22. 2026-06-11 00:35 UTCGHSA enrichment
  23. 2026-06-10 22:18 UTCEPSS rescore
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-10 13:22 UTCEPSS rescore
  26. 2026-06-09 22:48 UTCEG score recompute
  27. 2026-06-09 22:48 UTCGHSA enrichment
  28. 2026-06-08 20:51 UTCEG score recompute
  29. 2026-06-08 20:51 UTCGHSA enrichment
  30. 2026-06-08 14:17 UTCEPSS rescore
  31. 2026-06-08 14:17 UTCEPSS rescore
  32. 2026-06-07 17:42 UTCEG score recompute
  33. 2026-06-07 17:42 UTCGHSA enrichment
  34. 2026-06-07 15:25 UTCEPSS rescore
  35. 2026-06-07 15:25 UTCEPSS rescore
  36. 2026-06-06 16:06 UTCEG score recompute
  37. 2026-06-06 16:06 UTCGHSA enrichment
  38. 2026-06-06 13:47 UTCEPSS rescore
  39. 2026-06-06 13:47 UTCEPSS rescore
  40. 2026-06-05 22:47 UTCEPSS rescore
  41. 2026-06-05 14:30 UTCEG score recompute
  42. 2026-06-05 14:30 UTCGHSA enrichment
  43. 2026-06-05 06:10 UTCEPSS rescore
  44. 2026-06-05 06:10 UTCEPSS rescore
  45. 2026-06-04 13:12 UTCEPSS rescore
  46. 2026-06-04 13:12 UTCEPSS rescore
  47. 2026-06-04 12:54 UTCEG score recompute
  48. 2026-06-04 12:54 UTCGHSA enrichment
  49. 2026-06-03 11:18 UTCEG score recompute
  50. 2026-06-03 11:18 UTCGHSA enrichment
  51. 2026-06-02 20:13 UTCEPSS rescore
  52. 2026-06-02 09:42 UTCEG score recompute
  53. 2026-06-02 09:42 UTCGHSA enrichment
  54. 2026-06-01 13:52 UTCEPSS rescore
  55. 2026-06-01 13:52 UTCEPSS rescore
  56. 2026-06-01 08:06 UTCEG score recompute
  57. 2026-06-01 08:06 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 13:40 UTCEPSS rescore
  67. 2026-05-27 13:40 UTCEPSS rescore
  68. 2026-05-26 13:44 UTCEPSS rescore
  69. 2026-05-26 07:18 UTCEPSS rescore
  70. 2026-05-21 22:43 UTCEPSS rescore
  71. 2026-05-20 22:38 UTCEPSS rescore
  72. 2026-05-20 13:44 UTCEG score recompute
  73. 2026-05-20 13:44 UTCGHSA enrichment
  74. 2026-05-20 11:22 UTCEPSS rescore
  75. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43302?
CVE-2026-43302 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Set DMA segment size to avoid debug warnings When using V3D rendering with CONFIGDMAAPI_DEBUG enabled, the kernel occasionally reports a segment size mismatch. This is because 'maxsegsize' is not set. The kernel defaults…
When was CVE-2026-43302 disclosed?
CVE-2026-43302 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43302 actively exploited?
CVE-2026-43302 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43302?
CVE-2026-43302 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43302?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43302, 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-43302

Explore →

Is Your Infrastructure Affected by CVE-2026-43302?

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