NULL Pointer Dereference The advisory has been revoked - it doesn't affect any version of package perf6.18 (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about NULL Pointer Dereference vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-AMZN2023-PERF618-16740397
- published18 May 2026
- disclosed6 May 2026
Introduced: 6 May 2026
NewCVE-2026-43189 (opens in a new tab)Amendment
The Amazon-Linux security team deemed this advisory irrelevant for Amazon-Linux:2023.
NVD Description
Note: Versions mentioned in the description apply only to the upstream perf6.18 package and not the perf6.18 package as distributed by Amazon-Linux.
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.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-43189
- https://git.kernel.org/stable/c/2de0a3c8148fc3dbea21981e6569f550b3626119
- https://git.kernel.org/stable/c/30aaed311f973f13ba13a0cd2dc0202f595fff48
- https://git.kernel.org/stable/c/461733d83e67ba7e3a5b750c0d203f738e01244f
- https://git.kernel.org/stable/c/7345d6d356336c448d6b9230ed8704f39679fd12
- https://git.kernel.org/stable/c/b02bcb378efa8af07827f49b3afcc5e825318c55