CVE-2026-98915: media: video-i2c: use vb2_video_unregister_device on driver removal
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 56384b486b80ce4a2bc93689aae49995f908f90d, 82e432c9ebfa13fb8d47d6d550be5d7d2a84a8ab, 97adc8cd04df2085f7fd437838005f3bb16bafae; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 56384b486b80ce4a2bc93689aae49995f908f90d, 82e432c9ebfa13fb8d47d6d550be5d7d2a84a8ab, 97adc8cd04df2085f7fd437838005f3bb16bafae; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 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: video-i2c: use vb2_video_unregister_device on driver removal The driver uses vb2_fop_release() as its file release operation, so vb2_video_unregister_device() should be used instead of video_unregister_device() during driver removal. This ensures that the vb2 queue is properly disconnected before the video device is unregistered.
- Published
- Oct 23, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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
- 4.18affected
- 5cebaac609744414463d1ecc28fdecd26c1b9bc1 and later · before 97adc8cd04df2085f7fd437838005f3bb16bafaeaffected · git
- 5cebaac609744414463d1ecc28fdecd26c1b9bc1 and later · before b7afb0c24a761c2367e5fa87a9941d67d373c127affected · git
- 5cebaac609744414463d1ecc28fdecd26c1b9bc1 and later · before b8fba9f66019d4c83235c4219ff8edeb7e3af20daffected · git
- 5cebaac609744414463d1ecc28fdecd26c1b9bc1 and later · before 82e432c9ebfa13fb8d47d6d550be5d7d2a84a8abaffected · git
- 5cebaac609744414463d1ecc28fdecd26c1b9bc1 and later · before 56384b486b80ce4a2bc93689aae49995f908f90daffected · git
- before 4.18not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
- 6.12.111 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98913Oct 23, 2026 · net: thunderx: fix PTP device ref leak in nicvf_probe()0Monitor
- ← EarlierCVE-2026-98914Oct 23, 2026 · drm/amdgpu: cap ATOM command table nesting depth0Monitor
- Later →CVE-2026-98916Oct 23, 2026 · wifi: nl80211: check link is beaconing for color change0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 56384b486b80ce4a2bc93689aae49995f908f90d | Vendor (CNA) |
| Linux Linux | 82e432c9ebfa13fb8d47d6d550be5d7d2a84a8ab | Vendor (CNA) |
| Linux Linux | 97adc8cd04df2085f7fd437838005f3bb16bafae | Vendor (CNA) |
| Linux Linux | b7afb0c24a761c2367e5fa87a9941d67d373c127 | Vendor (CNA) |
| Linux Linux | b8fba9f66019d4c83235c4219ff8edeb7e3af20d | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package 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.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+21 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1390 · Oct 26, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: 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.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.