CVE-2025-39739

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-09-11. 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:

iommu/arm-smmu-qcom: Add SM6115 MDSS compatible

Add the SM6115 MDSS compatible to clients compatible list, as it also needs that workaround. Without this workaround, for example, QRB4210 RB2 which is based on SM4250/SM6115 generates a lot of smmu unhandled context faults during boot:

arm_smmu_context_fault: 116854 callbacks suppressed arm-smmu c600000.iommu: Unhandled context fault: fsr=0x402, iova=0x5c0ec600, fsynr=0x320021, cbfrsynra=0x420, cb=5 arm-smmu c600000.iommu: FSR = 00000402 [Format=2 TF], SID=0x420 arm-smmu c600000.iommu: FSYNR0 = 00320021 [S1CBNDX=50 PNU PLVL=1] arm-smmu c600000.iommu: Unhandled context fault: fsr=0x402, iova=0x5c0d7800, fsynr=0x320021, cbfrsynra=0x420, cb=5 arm-smmu c600000.iommu: FSR = 00000402 [Format=2 TF], SID=0x420

and also failed initialisation of lontium lt9611uxc, gpu and dpu is observed: (binding MDSS components triggered by lt9611uxc have failed)

------------[ cut here ]------------ !aspace WARNING: CPU: 6 PID: 324 at drivers/gpu/drm/msm/msm_gem_vma.c:130 msm_gem_vma_init+0x150/0x18c [msm] Modules linked in: ... (long list of modules) CPU: 6 UID: 0 PID: 324 Comm: (udev-worker) Not tainted 6.15.0-03037-gaacc73ceeb8b #4 PREEMPT Hardware name: Qualcomm Technologies, Inc. QRB4210 RB2 (DT) pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : msm_gem_vma_init+0x150/0x18c [msm] lr : msm_gem_vma_init+0x150/0x18c [msm] sp : ffff80008144b280 ... Call trace: msm_gem_vma_init+0x150/0x18c [msm] (P) get_vma_locked+0xc0/0x194 [msm] msm_gem_get_and_pin_iova_range+0x4c/0xdc [msm] msm_gem_kernel_new+0x48/0x160 [msm] msm_gpu_init+0x34c/0x53c [msm] adreno_gpu_init+0x1b0/0x2d8 [msm] a6xx_gpu_init+0x1e8/0x9e0 [msm] adreno_bind+0x2b8/0x348 [msm] component_bind_all+0x100/0x230 msm_drm_bind+0x13c/0x3d0 [msm] try_to_bring_up_aggregate_device+0x164/0x1d0 __component_add+0xa4/0x174 component_add+0x14/0x20 dsi_dev_attach+0x20/0x34 [msm] dsi_host_attach+0x58/0x98 [msm] devm_mipi_dsi_attach+0x34/0x90 lt9611uxc_attach_dsi.isra.0+0x94/0x124 [lontium_lt9611uxc] lt9611uxc_probe+0x540/0x5fc [lontium_lt9611uxc] i2c_device_probe+0x148/0x2a8 really_probe+0xbc/0x2c0 __driver_probe_device+0x78/0x120 driver_probe_device+0x3c/0x154 __driver_attach+0x90/0x1a0 bus_for_each_dev+0x68/0xb8 driver_attach+0x24/0x30 bus_add_driver+0xe4/0x208 driver_register+0x68/0x124 i2c_register_driver+0x48/0xcc lt9611uxc_driver_init+0x20/0x1000 [lontium_lt9611uxc] do_one_initcall+0x60/0x1d4 do_init_module+0x54/0x1fc load_module+0x1748/0x1c8c init_module_from_file+0x74/0xa0 __arm64_sys_finit_module+0x130/0x2f8 invoke_syscall+0x48/0x104 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x2c/0x80 el0t_64_sync_handler+0x10c/0x138 el0t_64_sync+0x198/0x19c ---[ end trace 0000000000000000 ]--- msm_dpu 5e01000.display-controller: [drm:msm_gpu_init [msm]] *ERROR* could not allocate memptrs: -22 msm_dpu 5e01000.display-controller: failed to load adreno gpu platform a400000.remoteproc:glink-edge:apr:service@7:dais: Adding to iommu group 19 msm_dpu 5e01000.display-controller: failed to bind 5900000.gpu (ops a3xx_ops [msm]): -22 msm_dpu 5e01000.display-controller: adev bind failed: -22 lt9611uxc 0-002b: failed to attach dsi to host lt9611uxc 0-002b: probe with driver lt9611uxc failed with error -22

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

Published

September 11, 2025

Last Modified

November 25, 2025

References (5)

Vendor Advisories for CVE-2025-39739(1)

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

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-29ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-29ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-29ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-29ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-05-29ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-05-29ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-29ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-29ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-29ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-29ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-29ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1044.44~22.04.1) @ jammy2026-05-29ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-29ubuntu
linuxKernel @ 6.6.103—osv

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.

Additional Vendor Advisories

(16)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2025-39739?
CVE-2025-39739 is a medium vulnerability published on September 11, 2025. In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-qcom: Add SM6115 MDSS compatible Add the SM6115 MDSS compatible to clients compatible list, as it also needs that workaround. Without this workaround, for example, QRB4210 RB2 which is based on SM4250/SM6115…
When was CVE-2025-39739 disclosed?
CVE-2025-39739 was first published in the National Vulnerability Database on September 11, 2025, with the most recent update on November 25, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-39739 actively exploited?
CVE-2025-39739 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 95.7% of all scored CVEs.
What is the CVSS score of CVE-2025-39739?
CVE-2025-39739 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-39739?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-39739, 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-2025-39739

Explore →

Is Your Infrastructure Affected by CVE-2025-39739?

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

Start Free Scan →Browse All CVEs