CVE-2026-43397

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.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/bridge: samsung-dsim: Fix memory leak in error path

In samsung_dsim_host_attach(), drm_bridge_add() is called to add the bridge. However, if samsung_dsim_register_te_irq() or pdata->host_ops->attach() fails afterwards, the function returns without removing the bridge, causing a memory leak.

Fix this by adding proper error handling with goto labels to ensure drm_bridge_remove() is called in all error paths. Also ensure that samsung_dsim_unregister_te_irq() is called if the attach operation fails after the TE IRQ has been registered.

samsung_dsim_unregister_te_irq() function is moved without changes to be before samsung_dsim_host_attach() to avoid forward declaration.

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
2%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 21, 2026

Advisory Details (5)

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

drm/bridge: samsung-dsim: Fix memory leak in error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/bridge: samsung-dsim: Fix memory leak in error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/bridge: samsung-dsim: Fix memory leak in error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98310fe3a2a79671b739a5344c1a11d74c503e25
generic

drm/bridge: samsung-dsim: Fix memory leak in error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/803ec1faf7c1823e6e3b1f2aaa81be18528c9436
generic

drm/bridge: samsung-dsim: Fix memory leak in error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b07f7d2c5a4078c2f1c11bb36685084fe4e5c95

Vendor Advisories for CVE-2026-43397(1)

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

Patch Availability(15)

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 (122 versions)6.19.10-1

Weakness Classification(1)

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

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 5× 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 189 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43397?
CVE-2026-43397 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/bridge: samsung-dsim: Fix memory leak in error path In samsungdsimhostattach(), drmbridge_add() is called to add the bridge. However, if samsungdsimregisterteirq() or pdata->host_ops->attach() fails afterwards, the function…
When was CVE-2026-43397 disclosed?
CVE-2026-43397 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43397 actively exploited?
CVE-2026-43397 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-43397?
CVE-2026-43397 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43397?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43397, 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-43397

Explore →

Is Your Infrastructure Affected by CVE-2026-43397?

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