CVE-2026-43189
Awaiting Analysis Awaiting Analysis - Queue
Memory Corruption in Linux Kernel V4L2 Async Subsystem

Publication date: 2026-05-06

Last updated on: 2026-05-06

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-06
Last Modified
2026-05-06
Generated
2026-05-07
AI Q&A
2026-05-06
EPSS Evaluated
N/A
NVD
CVE-2026-43189
EUVD
EUVD-2026-27751
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is in the Linux kernel's media subsystem, specifically in the v4l2-async component which handles asynchronous device connections.

The issue involves error handling after an asynchronous connection matches a firmware node (fwnode). When a match is found, a sub-device may be registered, its bound operation called, ancillary links created, and the connection added to the sub-device's list.

The vulnerability arises because if the function v4l2_async_match_notify() fails before handling sub-notifiers, the async connection is unbound and removed from the sub-device's connection list twice, causing inconsistent state.

Additionally, the async connection's sub-device field (sd) is set only after creating ancillary links, but it is dereferenced earlier during error handling, which can lead to use-after-free or null pointer dereference issues.


How can this vulnerability impact me? :

This vulnerability can cause improper error handling in the Linux kernel's media subsystem, potentially leading to system instability or crashes.

Because the async connection's sub-device field may be dereferenced before being properly set, this could result in kernel errors such as null pointer dereferences or use-after-free conditions.

Such kernel errors can cause denial of service by crashing the kernel or causing unpredictable behavior in media device handling.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart