High

CVE-2026-68222 — media: msi2500: Return queued buffers on start_streaming() failure

In the Linux kernel, the following vulnerability has been resolved: media: msi2500: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak. msi2500_start_streaming() had five error paths that all hit this trap and were further tangled by ret-overwriting between calls: - -ENODEV when the USB device was already disconnected - -ERESTARTSYS when mutex_lock_interruptible() was interrupted - msi2500_set_usb_adc() failure: ret was silently overwritten by the next call (msi2500_isoc_init), so the error was lost entirely - msi2500_isoc_init() failure: cleanup_queued_bufs was called, but the function then fell through to msi2500_ctrl_msg() and again masked the original error by overwriting ret - msi2500_ctrl_msg(CMD_START_STREAMING) failure: no cleanup at all, leaving isoc URBs submitted with no way for the driver to consume them Consolidate the error paths into a small goto chain. Every failure now stops the function, drains the queued-buffer list, and returns the real error code. The ctrl_msg failure path also rolls back the preceding msi2500_isoc_init() via msi2500_isoc_cleanup() before unlocking and draining. The cleanup helper takes a vb2_buffer_state argument so that the start_streaming error paths can pass VB2_BUF_STATE_QUEUED (as expected by userspace on start_streaming failure) while stop_streaming keeps its existing VB2_BUF_STATE_ERROR semantics. This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure").

Published Aug 10, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

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.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Linux

CVSS base

7.8

High · 2 source(s)

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	≥ 977e444f59ad16eedf66acae4f357011c74da291 and < c74b680704baecea4620c0774de473069e0bc4e8≥ 977e444f59ad16eedf66acae4f357011c74da291 and < 2d10eedb786a13f91d76e11320fabb0bf712519f≥ 977e444f59ad16eedf66acae4f357011c74da291 and < 2de14ddb4fea04ca616403a6ba81c5e8099e9b9e≥ 977e444f59ad16eedf66acae4f357011c74da291 and < 1d58229b330b7f67fbfa07e0f2a8a51fbeafaa9a≥ 977e444f59ad16eedf66acae4f357011c74da291 and < bab9d5a67d4db96ae8c187b92b37979911302a10≥ 977e444f59ad16eedf66acae4f357011c74da291 and < 264b5380c4f8aa92dbc2983ecd2b627f1d5e0061≥ 977e444f59ad16eedf66acae4f357011c74da291 and < 3673cb0a5711e910074d69201da9e1535c03f97a≥ 977e444f59ad16eedf66acae4f357011c74da291 and < 7201c17786a498497bca57752883b90914d405ac and 1 more version 3.12	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

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)

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.

endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 7.8
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 10, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

git.kernel.org/stable/c/264b5380c4f8aa92dbc2983ecd2b627f1d5e0061
NIST National Vulnerability Database
git.kernel.org/stable/c/c74b680704baecea4620c0774de473069e0bc4e8
NIST National Vulnerability Database
git.kernel.org/stable/c/1d58229b330b7f67fbfa07e0f2a8a51fbeafaa9a
NIST National Vulnerability Database
git.kernel.org/stable/c/3673cb0a5711e910074d69201da9e1535c03f97a
NIST National Vulnerability Database
git.kernel.org/stable/c/2d10eedb786a13f91d76e11320fabb0bf712519f
NIST National Vulnerability Database
git.kernel.org/stable/c/2de14ddb4fea04ca616403a6ba81c5e8099e9b9e
NIST National Vulnerability Database
git.kernel.org/stable/c/7201c17786a498497bca57752883b90914d405ac
NIST National Vulnerability Database
git.kernel.org/stable/c/bab9d5a67d4db96ae8c187b92b37979911302a10
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

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 FIRST EPSS score.
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-68222 is "media: msi2500: Return queued buffers on start_streaming() failure", 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. 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.