---
id: "CVE-2026-98915"
kind: "vulnerability"
aliases: ["CVE-2026-98915"]
title: "Linux kernel: video-i2c driver removal skips proper vb2 queue disconnect"
severity: "unknown"
cvss: null
epss: 0.00209
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["infrastructure", "linux-kernel", "media-drivers"]
not_affected_if: ["no-video-i2c-hardware"]
published_at: "2026-10-23T12:18:25+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98915", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-98915", "first_seen_at": "2026-10-25T12:38:50+00:00"}]
---

# Linux kernel: video-i2c driver removal skips proper vb2 queue disconnect

The video-i2c media driver in the Linux kernel unregistered its video device with the plain removal call instead of the vb2 variant, so the vb2 queue was not disconnected first on driver removal. The sources do not describe an attacker-reachable impact.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- unknown

## Fix

- unknown

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98915
- 2026-10-25T12:38:50+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-98915

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_