CVE-2025-39993

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-10-15. 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 — 4 sources updated this week

Also known asEUVD-2025-34580 (ENISA EUVD) · GHSA-2c3m-5h4x-9w2g (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: rc: fix races with imon_disconnect()

Syzbot reports a KASAN issue as below: BUG: KASAN: use-after-free in __create_pipe include/linux/usb.h:1945 [inline] BUG: KASAN: use-after-free in send_packet+0xa2d/0xbc0 drivers/media/rc/imon.c:627 Read of size 4 at addr ffff8880256fb000 by task syz-executor314/4465

CPU: 2 PID: 4465 Comm: syz-executor314 Not tainted 6.0.0-rc1-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:317 [inline] print_report.cold+0x2ba/0x6e9 mm/kasan/report.c:433 kasan_report+0xb1/0x1e0 mm/kasan/report.c:495 __create_pipe include/linux/usb.h:1945 [inline] send_packet+0xa2d/0xbc0 drivers/media/rc/imon.c:627 vfd_write+0x2d9/0x550 drivers/media/rc/imon.c:991 vfs_write+0x2d7/0xdd0 fs/read_write.c:576 ksys_write+0x127/0x250 fs/read_write.c:631 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

The iMON driver improperly releases the usb_device reference in imon_disconnect without coordinating with active users of the device.

Specifically, the fields usbdev_intf0 and usbdev_intf1 are not protected by the users counter (ictx->users). During probe, imon_init_intf0 or imon_init_intf1 increments the usb_device reference count depending on the interface. However, during disconnect, usb_put_dev is called unconditionally, regardless of actual usage.

As a result, if vfd_write or other operations are still in progress after disconnect, this can lead to a use-after-free of the usb_device pointer.

Thread 1 vfd_write Thread 2 imon_disconnect ... if usb_put_dev(ictx->usbdev_intf0) else usb_put_dev(ictx->usbdev_intf1) ... while send_packet if pipe = usb_sndintpipe( ictx->usbdev_intf0) UAF else pipe = usb_sndctrlpipe( ictx->usbdev_intf0, 0) UAF

Guard access to usbdev_intf0 and usbdev_intf1 after disconnect by checking ictx->disconnected in all writer paths. Add early return with -ENODEV in send_packet(), vfd_write(), lcd_write() and display_open() if the device is no longer present.

Set and read ictx->disconnected under ictx->lock to ensure memory synchronization. Acquire the lock in imon_disconnect() before setting the flag to synchronize with any ongoing operations.

Ensure writers exit early and safely after disconnect before the USB core proceeds with cleanup.

Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

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 SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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
4th
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-10-27). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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)60 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 Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

October 15, 2025

Last Modified

October 19, 2026

Advisory Details (9)

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

media: rc: fix races with imon_disconnect() - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: rc: fix races with imon_disconnect() - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: rc: fix races with imon_disconnect() - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: rc: fix races with imon_disconnect() - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: rc: fix races with imon_disconnect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9348976003e39754af344949579e824a0a210fc4
Web page

media: rc: fix races with imon_disconnect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71da40648741d15b302700b68973fe8b382aef3c
Web page

media: rc: fix races with imon_disconnect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71c52b073922d05e79e6de7fc7f5f38f927929a4
Web page

media: rc: fix races with imon_disconnect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71096a6161a25e84acddb89a9d77f138502d26ab
Web page

media: rc: fix races with imon_disconnect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e7fd93b9cc565b839bc55a6662475718963e156

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-fips-5.4 (5.4.0.1156.98) @ focal2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1097.101) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1039.40~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-37.37~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1071 (5.4.0-1071.75) @ focal2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1062 (5.15.0-1062.66) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.277.283) @ xenial2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-90.91) @ noble2026-10-27ubuntu
ubuntulinux-tools-gke (4.15.0.1181.198~16.04.1) @ xenial2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1044.50) @ noble2026-10-27ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1017.17) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1102.111~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-fips (4.4.0.1121.122) @ xenial2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1045.48+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1098.88) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1156.150) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.4 (5.4.0.1157.94) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1044.50+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.14.0-1017.17~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1151.161~18.04.1) @ bionic2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1092.90) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1021.22) @ noble2026-10-27ubuntu
redhatkernel-rt-0:3.10.0-1160.147.1.rt56.1299.el72026-03-03redhat
redhatkernel-0:3.10.0-1160.147.1.el72026-03-03redhat
redhatkernel-0:4.18.0-477.126.1.el8_82026-01-28redhat
redhatkernel-0:4.18.0-372.177.1.el8_62026-01-28redhat
redhatkernel-0:4.18.0-193.183.1.el8_22026-01-28redhat
redhatkernel-0:4.18.0-305.183.1.el8_42026-01-14redhat
redhatkernel-rt-0:4.18.0-553.92.1.rt7.433.el8_102026-01-12redhat
redhatkernel-0:4.18.0-553.92.1.el8_102026-01-12redhat
linuxKernel @ 5.4.301 (fixes >=2.6.35)—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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (47 versions)
  • every version up to 5.10.247-1: fixed in 5.10.247-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.153-1~deb11u1 (12 versions)
  • every version up to 6.1.158-1~deb11u1: fixed in 6.1.158-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (44 versions)
  • every version up to 6.1.158-1: fixed in 6.1.158-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.57-1~bpo12+1 (6 versions)
  • every version up to 6.12.57-1: fixed in 6.12.57-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (69 versions)
  • every version up to 6.16.11-1: fixed in 6.16.11-1
—

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 10× in last 7d / 44× 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 233 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 135 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-39993?
CVE-2025-39993 is a high-severity vulnerability; its CVE record was published on October 15, 2025. In the Linux kernel, the following vulnerability has been resolved: media: rc: fix races with imon_disconnect() Syzbot reports a KASAN issue as below: BUG: KASAN: use-after-free in __create_pipe include/linux/usb.h:1945 [inline] BUG: KASAN: use-after-free in send_packet+0xa2d/0xbc0…
When was the CVE record for CVE-2025-39993 published?
The CVE record for CVE-2025-39993 was published on October 15, 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-39993 actively exploited?
CVE-2025-39993 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39993?
CVE-2025-39993 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-39993?
A fix for CVE-2025-39993 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39993 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-39993

Explore →

Is Your Infrastructure Affected by CVE-2025-39993?

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