CVE-2026-43301

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. 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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

media: chips-media: wave5: Fix PM runtime usage count underflow

Replace pm_runtime_put_sync() with pm_runtime_dont_use_autosuspend() in the remove path to properly pair with pm_runtime_use_autosuspend() from probe. This allows pm_runtime_disable() to handle reference count cleanup correctly regardless of current suspend state.

The driver calls pm_runtime_put_sync() unconditionally in remove, but the device may already be suspended due to autosuspend configured in probe. When autosuspend has already suspended the device, the usage count is 0, and pm_runtime_put_sync() decrements it to -1.

This causes the following warning on module unload:

------------[ cut here ]------------ WARNING: CPU: 1 PID: 963 at kernel/kthread.c:1430 kthread_destroy_worker+0x84/0x98 ... vdec 30210000.video-codec: Runtime PM usage count underflow!

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
2%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 15, 2026

Advisory Details (3)

Auto-updated Jun 17, 2026
No patch confirmed yet.
generic

media: chips-media: wave5: Fix PM runtime usage count underflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38
generic

media: chips-media: wave5: Fix PM runtime usage count underflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a278a55ead50db2444c8f01410c7f5a68723990
generic

media: chips-media: wave5: Fix PM runtime usage count underflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0bffda02317989f8d5cdc2d4462a4110b1290cf0

Vendor Advisories for CVE-2026-43301(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.16—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.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 27× 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 179 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-43301?
CVE-2026-43301 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix PM runtime usage count underflow Replace pmruntimeputsync() with pmruntimedontuse_autosuspend() in the remove path to properly pair with pmruntimeuse_autosuspend() from probe. This allows…
When was CVE-2026-43301 disclosed?
CVE-2026-43301 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43301 actively exploited?
CVE-2026-43301 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-43301?
CVE-2026-43301 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43301?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43301, 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-43301

Explore →

Is Your Infrastructure Affected by CVE-2026-43301?

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

Start Free Scan →Browse All CVEs