Answer in brief
CVE-2026-43189 records a Unknown severity vulnerability in media: v4l2-async: Fix error handling on steps after finding a match. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=28a1295795d85a25f2e7dd391c43969e95fcb341 <30aaed311f973f13ba13a0cd2dc0202f595fff48 || >=28a1295795d85a25f2e7dd391c43969e95fcb341 <461733d83e67ba7e3a5b750c0d203f738e01244f || >=28a1295795d85a25f2e7dd391c43969e95fcb341 <b02bcb378efa8af07827f49b3afcc5e825318c55 || >=28a1295795d85a25f2e7dd391c43969e95fcb341 <2de0a3c8148fc3dbea21981e6569f550b3626119 || >=28a1295795d85a25f2e7dd391c43969e95fcb341 <7345d6d356336c448d6b9230ed8704f39679fd12 | 30aaed311f973f13ba13a0cd2dc0202f595fff48, 461733d83e67ba7e3a5b750c0d203f738e01244f, b02bcb378efa8af07827f49b3afcc5e825318c55, 2de0a3c8148fc3dbea21981e6569f550b3626119, 7345d6d356336c448d6b9230ed8704f39679fd12 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.