CVE-2026-43189 Details
Description
In the Linux kernel, the following vulnerability has been resolved: media: v4l2-async: Fix error handling on steps after finding a match Once an async connection is found to be matching with an fwnode, a sub-device may be registered (in case it wasn't already), its bound operation is called, ancillary links are created, the async connection is added to the sub-device's list of connections and removed from the global waiting connection list. Further on, the sub-device's possible own notifier is searched for possible additional matches. Fix these specific issues: - If v4l2_async_match_notify() failed before the sub-notifier handling, the async connection was unbound and its entry removed from the sub-device's async connection list. The latter part was also done in v4l2_async_match_notify(). - The async connection's sd field was only set after creating ancillary links in v4l2_async_match_notify(). It was however dereferenced in v4l2_async_unbind_subdev_one(), which was called on error path of v4l2_async_match_notify() failure.
A vulnerability in the Linux kernel's V4L2 asynchronous handling can lead to improper error management when establishing connections with sub-devices. This issue arises in the V4L2 asynchronous notifier system, where connections are matched with function nodes, and can result in sub-devices being incorrectly registered or unregistered during the error handling process. The vulnerability is present in the Linux kernel stable tree.
Users can update to the latest version of the Linux kernel where this vulnerability has been addressed. Instructions for downloading the patched version can be found in the Linux kernel documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2de0a3c8148fc3dbea21981e6569f550b3626119 | kernel.org | Patch |
| https://git.kernel.org/stable/c/30aaed311f973f13ba13a0cd2dc0202f595fff48 | kernel.org | Patch |
| https://git.kernel.org/stable/c/461733d83e67ba7e3a5b750c0d203f738e01244f | kernel.org | Patch |
| https://git.kernel.org/stable/c/7345d6d356336c448d6b9230ed8704f39679fd12 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b02bcb378efa8af07827f49b3afcc5e825318c55 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.6, < 6.6.128 >= 6.7, < 6.12.75 >= 6.13, < 6.18.16 >= 6.19, < 6.19.6 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 11, 2026 | Initial Analysis | [email protected] |
| May 6, 2026 | New CVE Received | kernel.org |