Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39993: media: rc: fix races with imon_disconnect()

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2e7fd93b9cc565b839bc55a6662475718963e156, 71096a6161a25e84acddb89a9d77f138502d26ab, 71c52b073922d05e79e6de7fc7f5f38f927929a4.

Low priority for now. Upgrade to Linux Linux 2e7fd93b9cc565b839bc55a6662475718963e156, 71096a6161a25e84acddb89a9d77f138502d26ab, 71c52b073922d05e79e6de7fc7f5f38f927929a4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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: <TASK> __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.

Published
Oct 15, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-39993

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.35affected
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before 9348976003e39754af344949579e824a0a210fc4affected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before b03fac6e2a38331faf8510b480becfa90cea1c9faffected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before 71c52b073922d05e79e6de7fc7f5f38f927929a4affected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before 71096a6161a25e84acddb89a9d77f138502d26abaffected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before 71da40648741d15b302700b68973fe8b382aef3caffected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before fd5d3e6b149ec8cce045d86a2b5e3664d6b32ba5affected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before d9f6ce99624a41c3bcb29a8d7d79b800665229ddaffected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before 2e7fd93b9cc565b839bc55a6662475718963e156affected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before fa0f61cc1d828178aa921475a9b786e7fbb65ccbaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.92.1.el8_104.18.0-553.92.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.92.1.rt7.433.el8_104.18.0-553.92.1.rt7.433.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.92.1.rt7.433.el8_104.18.0-553.92.1.rt7.433.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.92.1.rt7.433.el8_104.18.0-553.92.1.rt7.433.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.92.1.rt7.433.el8_104.18.0-553.92.1.rt7.433.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.92.1.rt7.433.el8_104.18.0-553.92.1.rt7.433.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.92.1.rt7.433.el8_104.18.0-553.92.1.rt7.433.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.92.1.rt7.433.el8_104.18.0-553.92.1.rt7.433.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.92.1.rt7.433.el8_104.18.0-553.92.1.rt7.433.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.92.1.rt7.433.el8_104.18.0-553.92.1.rt7.433.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-39991Oct 15, 2025 · wifi: ath11k: fix NULL dereference in ath11k_qmi_m3_load()
    0Monitor
  • ← EarlierCVE-2025-39992Oct 15, 2025 · mm: swap: check for stable address space before operating on the VMA
    0Monitor
  • Later →CVE-2025-39994Oct 15, 2025 · media: tuner: xc5000: Fix use-after-free in xc5000_release
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2e7fd93b9cc565b839bc55a6662475718963e156Vendor (CNA)
Linux Linux71096a6161a25e84acddb89a9d77f138502d26abVendor (CNA)
Linux Linux71c52b073922d05e79e6de7fc7f5f38f927929a4Vendor (CNA)
Linux Linux71da40648741d15b302700b68973fe8b382aef3cVendor (CNA)
Linux Linux9348976003e39754af344949579e824a0a210fc4Vendor (CNA)
Linux Linuxb03fac6e2a38331faf8510b480becfa90cea1c9fVendor (CNA)
Linux Linuxd9f6ce99624a41c3bcb29a8d7d79b800665229ddVendor (CNA)
Linux Linuxfa0f61cc1d828178aa921475a9b786e7fbb65ccbVendor (CNA)
Linux Linuxfd5d3e6b149ec8cce045d86a2b5e3664d6b32ba5Vendor (CNA)
almalinux:bpftool4.18.0-553.92.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.92.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.92.1.rt7.433.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.158-1 · Debian:12Package registry (OSV)
opensuse:kernel-source6.17.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-source-longterm6.18.16-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:kernel-rt0:4.18.0-553.92.1.rt7.433.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.92.1.rt7.433.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.92.1.rt7.433.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.92.1.rt7.433.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.92.1.rt7.433.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.92.1.rt7.433.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+8

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records