CVE-2026-43189

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-06. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 11, 2026

Advisory Details (5)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

media: v4l2-async: Fix error handling on steps after finding a match - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b02bcb378efa8af07827f49b3afcc5e825318c55
generic

media: v4l2-async: Fix error handling on steps after finding a match - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7345d6d356336c448d6b9230ed8704f39679fd12
generic

media: v4l2-async: Fix error handling on steps after finding a match - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/461733d83e67ba7e3a5b750c0d203f738e01244f
generic

media: v4l2-async: Fix error handling on steps after finding a match - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30aaed311f973f13ba13a0cd2dc0202f595fff48
generic

media: v4l2-async: Fix error handling on steps after finding a match - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2de0a3c8148fc3dbea21981e6569f550b3626119

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
linuxKernel @ 6.6.128—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1—

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 192 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 16:23 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-23 20:02 UTCEG score recompute
  19. 2026-08-23 20:02 UTCVendor advisory
  20. 2026-08-23 20:02 UTCGHSA enrichment
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:04 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-17 12:57 UTCEG score recompute
  3. 2026-08-17 12:57 UTCVendor advisory
  4. 2026-08-17 12:57 UTCGHSA enrichment
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 04:53 UTCEG score recompute
  7. 2026-08-16 04:53 UTCVendor advisory
  8. 2026-08-16 04:53 UTCGHSA enrichment
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:46 UTCEG score recompute
  11. 2026-08-15 01:46 UTCVendor advisory
  12. 2026-08-15 01:46 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 03:28 UTCEG score recompute
  15. 2026-08-14 03:28 UTCVendor advisory
  16. 2026-08-14 03:28 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 22:08 UTCEG score recompute
  19. 2026-08-12 22:08 UTCVendor advisory
  20. 2026-08-12 22:08 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-11 23:50 UTCEG score recompute
  23. 2026-08-11 23:50 UTCVendor advisory
  24. 2026-08-11 23:50 UTCGHSA enrichment
  25. 2026-08-11 13:43 UTCEPSS rescore
  26. 2026-08-11 01:32 UTCEG score recompute
  27. 2026-08-11 01:32 UTCVendor advisory
  28. 2026-08-11 01:32 UTCGHSA enrichment
  29. 2026-08-11 00:00 UTCEPSS rescore
  30. 2026-08-10 00:54 UTCEG score recompute
  31. 2026-08-10 00:54 UTCVendor advisory
  32. 2026-08-10 00:54 UTCGHSA enrichment
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 02:36 UTCEG score recompute
  35. 2026-08-09 02:36 UTCVendor advisory
  36. 2026-08-09 02:36 UTCGHSA enrichment
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-07 19:02 UTCEG score recompute
  39. 2026-08-07 19:02 UTCVendor advisory
  40. 2026-08-07 19:02 UTCGHSA enrichment
  41. 2026-08-06 20:43 UTCEG score recompute
  42. 2026-08-06 20:43 UTCVendor advisory
  43. 2026-08-06 20:43 UTCGHSA enrichment
  44. 2026-08-06 13:46 UTCEPSS rescore
  45. 2026-08-05 22:21 UTCEG score recompute
  46. 2026-08-05 22:21 UTCVendor advisory
  47. 2026-08-05 22:21 UTCGHSA enrichment
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-04 15:10 UTCEPSS rescore
  50. 2026-08-04 10:38 UTCEPSS rescore
  51. 2026-08-04 02:19 UTCEG score recompute
  52. 2026-08-04 02:19 UTCVendor advisory
  53. 2026-08-04 02:19 UTCGHSA enrichment
  54. 2026-08-03 10:36 UTCEPSS rescore
  55. 2026-08-03 03:59 UTCVendor advisory
  56. 2026-08-03 03:59 UTCGHSA enrichment
  57. 2026-08-02 05:08 UTCEG score recompute
  58. 2026-08-02 05:08 UTCVendor advisory
  59. 2026-08-02 05:08 UTCGHSA enrichment
  60. 2026-08-02 02:27 UTCEPSS rescore
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-07-30 16:28 UTCEPSS rescore
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-28 15:36 UTCEPSS rescore
  65. 2026-07-27 14:13 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-25 14:18 UTCEPSS rescore
  69. 2026-07-24 14:17 UTCEPSS rescore
  70. 2026-07-23 14:18 UTCEPSS rescore
  71. 2026-07-23 03:13 UTCEG score recompute
  72. 2026-07-22 14:08 UTCEPSS rescore
  73. 2026-07-21 15:24 UTCEPSS rescore
  74. 2026-07-20 22:02 UTCOSV refresh
  75. 2026-07-20 17:08 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43189?
CVE-2026-43189 is a medium vulnerability published on May 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,…
When was CVE-2026-43189 disclosed?
CVE-2026-43189 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43189 actively exploited?
CVE-2026-43189 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-43189?
CVE-2026-43189 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43189?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43189, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43189

Explore →

Is Your Infrastructure Affected by CVE-2026-43189?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs