CVE-2026-89870 — media: zoran: Avoid freeing a registered video_device twice
In the Linux kernel, the following vulnerability has been resolved: media: zoran: Avoid freeing a registered video_device twice zoran_init_video_device() installs zoran_vdev_release() as the video_device release callback through zoran_template. After video_register_device() succeeds, video_unregister_device() drops the registered video_device reference and the V4L2 core eventually invokes that release callback, which kfree()s the video_device. zoran_exit_video_devices() called video_unregister_device() and then kfree(zr->video_dev), so device teardown could free the same video_device twice. Remove the direct kfree() and clear the cached pointer after unregistering. The pre-registration failure path keeps its manual free because the video_device was not registered there. This issue was found by a static analysis checker and confirmed by manual source review.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 82e3a496eb56da0b9f29fdc5b63cedb3289e91de and < 3ad6cf27505017a6794f5f96c31218c2291e951b≥ 82e3a496eb56da0b9f29fdc5b63cedb3289e91de and < c4acac8cdc005b2d14b6cef5e215d264212857f3≥ 82e3a496eb56da0b9f29fdc5b63cedb3289e91de and < 4d99d8d0d895489064783601a516bd45812fa992≥ 82e3a496eb56da0b9f29fdc5b63cedb3289e91de and < f1c4f3885df1f09bcab5296d86834d104f865e86≥ 82e3a496eb56da0b9f29fdc5b63cedb3289e91de and < 672dbccf4351370dad002d3c78dbb29ca1588f22≥ 82e3a496eb56da0b9f29fdc5b63cedb3289e91de and < 0735e0b5a96761a9ce277a238e834008ad92a0a5version bd01629315ffd5b63da91d0bd529a77d30e55028version ff3357bffd9fb78f59762d8955afc7382a279079 and 7 moreversion c1ba65100a359fe28cfe37e09e10c99f247cbf1eversion 1e501ec38796f43e995731d1bcd4173cb1ccfce0≥ 5.10.110 and < 5.11≥ 5.15.33 and < 5.16≥ 5.16.19 and < 5.17≥ 5.17.2 and < 5.18version 5.18 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
6 on the record
- git.kernel.org/stable/c/672dbccf4351370dad002d3c78dbb29ca1588f22
- git.kernel.org/stable/c/c4acac8cdc005b2d14b6cef5e215d264212857f3
- git.kernel.org/stable/c/0735e0b5a96761a9ce277a238e834008ad92a0a5
- git.kernel.org/stable/c/3ad6cf27505017a6794f5f96c31218c2291e951b
- git.kernel.org/stable/c/f1c4f3885df1f09bcab5296d86834d104f865e86
- git.kernel.org/stable/c/4d99d8d0d895489064783601a516bd45812fa992
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 2d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 2d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 3d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 3d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 3d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89870 is "media: zoran: Avoid freeing a registered video_device twice", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.