Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68194: media: imon: make send_packet() more robust

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 0213e4175abbb9dfcbf7c197e3817d527f459ad5, 26f6a1dd5d81ad61a875a747698da6f27abf389b, 519737af11c03590819a6eec2ad532cfdb87ea63.

Low priority for now. Upgrade to Linux Linux 0213e4175abbb9dfcbf7c197e3817d527f459ad5, 26f6a1dd5d81ad61a875a747698da6f27abf389b, 519737af11c03590819a6eec2ad532cfdb87ea63 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: imon: make send_packet() more robust syzbot is reporting that imon has three problems which result in hung tasks due to forever holding device lock [1]. First problem is that when usb_rx_callback_intf0() once got -EPROTO error after ictx->dev_present_intf0 became true, usb_rx_callback_intf0() resubmits urb after printk(), and resubmitted urb causes usb_rx_callback_intf0() to again get -EPROTO error. This results in printk() flooding (RCU stalls). Alan Stern commented [2] that In theory it's okay to resubmit _if_ the driver has a robust error-recovery scheme (such as giving up after some fixed limit on the number of errors or after some fixed time has elapsed, perhaps with a time delay to prevent a flood of errors). Most drivers don't bother to do this; they simply give up right away. This makes them more vulnerable to short-term noise interference during USB transfers, but in reality such interference is quite rare. There's nothing really wrong with giving up right away. but imon has a poor error-recovery scheme which just retries forever; this behavior should be fixed. Since I'm not sure whether it is safe for imon users to give up upon any error code, this patch takes care of only union of error codes chosen from modules in drivers/media/rc/ directory which handle -EPROTO error (i.e. ir_toy, mceusb and igorplugusb). Second problem is that when usb_rx_callback_intf0() once got -EPROTO error before ictx->dev_present_intf0 becomes true, usb_rx_callback_intf0() always resubmits urb due to commit 8791d63af0cf ("[media] imon: don't wedge hardware after early callbacks"). Move the ictx->dev_present_intf0 test introduced by commit 6f6b90c9231a ("[media] imon: don't parse scancodes until intf configured") to immediately before imon_incoming_packet(), or the first problem explained above happens without printk() flooding (i.e. hung task). Third problem is that when usb_rx_callback_intf0() is not called for some reason (e.g. flaky hardware; the reproducer for this problem sometimes prevents usb_rx_callback_intf0() from being called), wait_for_completion_interruptible() in send_packet() never returns (i.e. hung task). As a workaround for such situation, change send_packet() to wait for completion with timeout of 10 seconds.

Published
Dec 16, 2025
Updated
Oct 14, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-68194

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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
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 519737af11c03590819a6eec2ad532cfdb87ea63affected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before f58ab83b7b7133e6baefe03a46846c4f6ce45e2faffected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before 26f6a1dd5d81ad61a875a747698da6f27abf389baffected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before 667afd4681781f60a644cd0d2ee6c59cb1c36208affected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before 8231e80118463be5598daaf266c1c83650f1948baffected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before 0213e4175abbb9dfcbf7c197e3817d527f459ad5affected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before f7f3ecb4934fff782fa9bb1cd16e2290c041b22daffected · git
    • 21677cfc562a27e099719d413287bc8d1d24deb7 and later · before eecd203ada43a4693ce6fdd3a58ae10c7819252caffected · git
    • before 2.6.35not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.159-16.1.159-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.8-16.17.8-1

Same product

linux: all records

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-68192Dec 16, 2025 · net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup
    39Monitor
  • ← EarlierCVE-2025-68193Dec 16, 2025 · drm/xe/guc: Add devm release action to safely tear down CT
    0Monitor
  • Later →CVE-2025-68196Dec 16, 2025 · drm/amd/display: Cache streams targeting link when performing LT automation
    0Monitor

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 Linux0213e4175abbb9dfcbf7c197e3817d527f459ad5Vendor (CNA)
Linux Linux26f6a1dd5d81ad61a875a747698da6f27abf389bVendor (CNA)
Linux Linux519737af11c03590819a6eec2ad532cfdb87ea63Vendor (CNA)
Linux Linux667afd4681781f60a644cd0d2ee6c59cb1c36208Vendor (CNA)
Linux Linux8231e80118463be5598daaf266c1c83650f1948bVendor (CNA)
Linux Linuxeecd203ada43a4693ce6fdd3a58ae10c7819252cVendor (CNA)
Linux Linuxf58ab83b7b7133e6baefe03a46846c4f6ce45e2fVendor (CNA)
Linux Linuxf7f3ecb4934fff782fa9bb1cd16e2290c041b22dVendor (CNA)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records