CVE-2025-68175

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-16. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2025-203721 (ENISA EUVD) · GHSA-j5pm-p7rh-c37w (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

media: nxp: imx8-isi: Fix streaming cleanup on release

The current implementation unconditionally calls mxc_isi_video_cleanup_streaming() in mxc_isi_video_release(). This can lead to situations where any release call (like from a simple "v4l2-ctl -l") may release a currently streaming queue when called on such a device.

This is reproducible on an i.MX8MP board by streaming from an ISI capture device using gstreamer:

gst-launch-1.0 -v v4l2src device=/dev/videoX ! \ video/x-raw,format=GRAY8,width=1280,height=800,framerate=1/120 ! \ fakesink

While this stream is running, querying the caps of the same device provokes the error state:

v4l2-ctl -l -d /dev/videoX

This results in the following trace:

[ 155.452152] ------------[ cut here ]------------ [ 155.452163] WARNING: CPU: 0 PID: 1708 at drivers/media/platform/nxp/imx8-isi/imx8-isi-pipe.c:713 mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] [ 157.004248] Modules linked in: cfg80211 rpmsg_ctrl rpmsg_char rpmsg_tty virtio_rpmsg_bus rpmsg_ns rpmsg_core rfkill nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables mcp251x6 [ 157.053499] CPU: 0 UID: 0 PID: 1708 Comm: python3 Not tainted 6.15.4-00114-g1f61ca5cad76 #1 PREEMPT [ 157.064369] Hardware name: imx8mp_board_01 (DT) [ 157.068205] pstate: 400000c5 (nZcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 157.075169] pc : mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] [ 157.081195] lr : mxc_isi_pipe_irq_handler+0x38/0x1b0 [imx8_isi] [ 157.087126] sp : ffff800080003ee0 [ 157.090438] x29: ffff800080003ee0 x28: ffff0000c3688000 x27: 0000000000000000 [ 157.097580] x26: 0000000000000000 x25: ffff0000c1e7ac00 x24: ffff800081b5ad50 [ 157.104723] x23: 00000000000000d1 x22: 0000000000000000 x21: ffff0000c25e4000 [ 157.111866] x20: 0000000060000200 x19: ffff80007a0608d0 x18: 0000000000000000 [ 157.119008] x17: ffff80006a4e3000 x16: ffff800080000000 x15: 0000000000000000 [ 157.126146] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ 157.133287] x11: 0000000000000040 x10: ffff0000c01445f0 x9 : ffff80007a053a38 [ 157.140425] x8 : ffff0000c04004b8 x7 : 0000000000000000 x6 : 0000000000000000 [ 157.147567] x5 : ffff0000c0400490 x4 : ffff80006a4e3000 x3 : ffff0000c25e4000 [ 157.154706] x2 : 0000000000000000 x1 : ffff8000825c0014 x0 : 0000000060000200 [ 157.161850] Call trace: [ 157.164296] mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] (P) [ 157.170319] __handle_irq_event_percpu+0x58/0x218 [ 157.175029] handle_irq_event+0x54/0xb8 [ 157.178867] handle_fasteoi_irq+0xac/0x248 [ 157.182968] handle_irq_desc+0x48/0x68 [ 157.186723] generic_handle_domain_irq+0x24/0x38 [ 157.191346] gic_handle_irq+0x54/0x120 [ 157.195098] call_on_irq_stack+0x24/0x30 [ 157.199027] do_interrupt_handler+0x88/0x98 [ 157.203212] el0_interrupt+0x44/0xc0 [ 157.206792] __el0_irq_handler_common+0x18/0x28 [ 157.211328] el0t_64_irq_handler+0x10/0x20 [ 157.215429] el0t_64_irq+0x198/0x1a0 [ 157.219009] ---[ end trace 0000000000000000 ]---

Address this issue by moving the streaming preparation and cleanup to the vb2 .prepare_streaming() and .unprepare_streaming() operations. This also simplifies the driver by allowing direct usage of the vb2_ioctl_streamon() and vb2_ioctl_streamoff() helpers, and removal of the manual cleanup from mxc_isi_video_release().

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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
7th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-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-11-05). 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

December 16, 2025

Last Modified

October 21, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
Patch available.
Web page

media: nxp: imx8-isi: Fix streaming cleanup on release - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: nxp: imx8-isi: Fix streaming cleanup on release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47773031a148ad7973b809cc7723cba77eda2b42
Web page

media: nxp: imx8-isi: Fix streaming cleanup on release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/029914306b93b37c6e7060793d2b6f76b935cfa6

Vendor Advisories for CVE-2025-68175(2)

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

Patch Availability(22)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-10-29ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-29ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-29ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-29ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-29ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-10-29ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-10-29ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-29ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-10-29ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-29ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-29ubuntu
linuxKernel @ 6.17.8 (fixes >=6.4.0)—osv
linuxKernel @ 6.12.80 (fixes >=6.4.0)—osv
linuxKernel @ 6.6.160 (fixes >=6.4.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.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.8-1~bpo13+1 (79 versions)
  • every version up to 6.17.8-1: fixed in 6.17.8-1
—

All Vendor Advisories

(19)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 52× 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 99 of 258 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 159 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-68175?
CVE-2025-68175 is a high-severity vulnerability; its CVE record was published on December 16, 2025. In the Linux kernel, the following vulnerability has been resolved: media: nxp: imx8-isi: Fix streaming cleanup on release The current implementation unconditionally calls mxc_isi_video_cleanup_streaming() in mxc_isi_video_release(). This can lead to situations where any release call (like from a…
When was the CVE record for CVE-2025-68175 published?
The CVE record for CVE-2025-68175 was published on December 16, 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 21, 2026; the record at its source may have been updated since.
Is CVE-2025-68175 actively exploited?
CVE-2025-68175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-68175?
CVE-2025-68175 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-68175?
A fix for CVE-2025-68175 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-68175 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-68175

Explore →

Is Your Infrastructure Affected by CVE-2025-68175?

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

Book a Demo →Browse All CVEs