CVE-2025-39739

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-28972 (ENISA EUVD) · GHSA-79cf-57gq-fhm9 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

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.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2025

Last Modified

October 19, 2026

Advisory Details (5)

Auto-updated Oct 19, 2026
Patch available.
Web page

iommu/arm-smmu-qcom: Add SM6115 MDSS compatible - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f7fa8520f30373ce99c436c4d57c76befdacbef3
Web page

iommu/arm-smmu-qcom: Add SM6115 MDSS compatible - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e52bbaa209ebff3bf7a10c17ba7d3e1d3cb0fe61
Web page

iommu/arm-smmu-qcom: Add SM6115 MDSS compatible - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c62963370627f3aa22d991e0a3e93f5d61ad9b08
Web page

iommu/arm-smmu-qcom: Add SM6115 MDSS compatible - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a11b6ee7cab87c4d75e95ac9e7443155f7cecb55
Web page

iommu/arm-smmu-qcom: Add SM6115 MDSS compatible - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d470cf40c9265092eb33c3d3d9dc8bad452bcc2

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-19ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-19ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-19ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-19ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-19ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-19ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1044.44~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-19ubuntu
linuxKernel @ 6.6.103 (fixes >=6.2.0)—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.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1~bpo12+1
  • every version up to 6.12.43-1: fixed in 6.12.43-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (62 versions)
  • every version up to 6.16.3-1: fixed in 6.16.3-1
—

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 7× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 196 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 98 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-39739?
CVE-2025-39739 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2025-39739 published?
The CVE record for CVE-2025-39739 was published on September 11, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-39739 actively exploited?
CVE-2025-39739 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-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?
A fix for CVE-2025-39739 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39739 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs