{"api_version":"1","generated_at":"2026-05-30T23:32:31+00:00","cve":"CVE-2026-43301","urls":{"html":"https://cve.report/CVE-2026-43301","api":"https://cve.report/api/cve/CVE-2026-43301.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-43301","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-43301"},"summary":{"title":"media: chips-media: wave5: Fix PM runtime usage count underflow","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Fix PM runtime usage count underflow\n\nReplace pm_runtime_put_sync() with pm_runtime_dont_use_autosuspend() in\nthe remove path to properly pair with pm_runtime_use_autosuspend() from\nprobe. This allows pm_runtime_disable() to handle reference count cleanup\ncorrectly regardless of current suspend state.\n\nThe driver calls pm_runtime_put_sync() unconditionally in remove, but the\ndevice may already be suspended due to autosuspend configured in probe.\nWhen autosuspend has already suspended the device, the usage count is 0,\nand pm_runtime_put_sync() decrements it to -1.\n\nThis causes the following warning on module unload:\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 1 PID: 963 at kernel/kthread.c:1430\n    kthread_destroy_worker+0x84/0x98\n  ...\n  vdec 30210000.video-codec: Runtime PM usage count underflow!","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-08 14:16:37","updated_at":"2026-05-15 13:37:05"},"problem_types":["CWE-191"],"metrics":[{"version":"3.1","source":"nvd@nist.gov","type":"Primary","score":"5.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","baseScore":5.5,"baseSeverity":"MEDIUM","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"}}],"references":[{"url":"https://git.kernel.org/stable/c/3a278a55ead50db2444c8f01410c7f5a68723990","name":"https://git.kernel.org/stable/c/3a278a55ead50db2444c8f01410c7f5a68723990","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38","name":"https://git.kernel.org/stable/c/9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0bffda02317989f8d5cdc2d4462a4110b1290cf0","name":"https://git.kernel.org/stable/c/0bffda02317989f8d5cdc2d4462a4110b1290cf0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-43301","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43301","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9707a6254a8a6b978bde811a44fe07d86c229d1c 3a278a55ead50db2444c8f01410c7f5a68723990 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9707a6254a8a6b978bde811a44fe07d86c229d1c 0bffda02317989f8d5cdc2d4462a4110b1290cf0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9707a6254a8a6b978bde811a44fe07d86c229d1c 9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.8","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.8 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.16 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19.6 6.19.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2026","cve_id":"43301","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"linux","cpe5":"linux_kernel","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"43301","cve":"CVE-2026-43301","epss":"0.000170000","percentile":"0.041320000","score_date":"2026-05-12","updated_at":"2026-05-13 00:11:53"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/media/platform/chips-media/wave5/wave5-vpu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"3a278a55ead50db2444c8f01410c7f5a68723990","status":"affected","version":"9707a6254a8a6b978bde811a44fe07d86c229d1c","versionType":"git"},{"lessThan":"0bffda02317989f8d5cdc2d4462a4110b1290cf0","status":"affected","version":"9707a6254a8a6b978bde811a44fe07d86c229d1c","versionType":"git"},{"lessThan":"9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38","status":"affected","version":"9707a6254a8a6b978bde811a44fe07d86c229d1c","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/media/platform/chips-media/wave5/wave5-vpu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.8"},{"lessThan":"6.8","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.16","versionType":"semver"},{"lessThanOrEqual":"6.19.*","status":"unaffected","version":"6.19.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.0","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.16","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.19.6","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0","versionStartIncluding":"6.8","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Fix PM runtime usage count underflow\n\nReplace pm_runtime_put_sync() with pm_runtime_dont_use_autosuspend() in\nthe remove path to properly pair with pm_runtime_use_autosuspend() from\nprobe. This allows pm_runtime_disable() to handle reference count cleanup\ncorrectly regardless of current suspend state.\n\nThe driver calls pm_runtime_put_sync() unconditionally in remove, but the\ndevice may already be suspended due to autosuspend configured in probe.\nWhen autosuspend has already suspended the device, the usage count is 0,\nand pm_runtime_put_sync() decrements it to -1.\n\nThis causes the following warning on module unload:\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 1 PID: 963 at kernel/kthread.c:1430\n    kthread_destroy_worker+0x84/0x98\n  ...\n  vdec 30210000.video-codec: Runtime PM usage count underflow!"}],"providerMetadata":{"dateUpdated":"2026-05-11T22:21:54.560Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/3a278a55ead50db2444c8f01410c7f5a68723990"},{"url":"https://git.kernel.org/stable/c/0bffda02317989f8d5cdc2d4462a4110b1290cf0"},{"url":"https://git.kernel.org/stable/c/9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38"}],"title":"media: chips-media: wave5: Fix PM runtime usage count underflow","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-43301","datePublished":"2026-05-08T13:11:22.234Z","dateReserved":"2026-05-01T14:12:56.000Z","dateUpdated":"2026-05-11T22:21:54.560Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-08 14:16:37","lastModifiedDate":"2026-05-15 13:37:05","problem_types":["CWE-191"],"metrics":{"cvssMetricV31":[{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","baseScore":5.5,"baseSeverity":"MEDIUM","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":3.6}]},"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.8","versionEndExcluding":"6.18.16","matchCriteriaId":"12C05E5A-F731-4E9B-94E0-2E3F7FBA69A3"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.19","versionEndExcluding":"6.19.6","matchCriteriaId":"373EEEDA-FAA1-4FB4-B6ED-DB4DD99DBE67"}]}]}]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"43301","Ordinal":"1","Title":"media: chips-media: wave5: Fix PM runtime usage count underflow","CVE":"CVE-2026-43301","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"43301","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Fix PM runtime usage count underflow\n\nReplace pm_runtime_put_sync() with pm_runtime_dont_use_autosuspend() in\nthe remove path to properly pair with pm_runtime_use_autosuspend() from\nprobe. This allows pm_runtime_disable() to handle reference count cleanup\ncorrectly regardless of current suspend state.\n\nThe driver calls pm_runtime_put_sync() unconditionally in remove, but the\ndevice may already be suspended due to autosuspend configured in probe.\nWhen autosuspend has already suspended the device, the usage count is 0,\nand pm_runtime_put_sync() decrements it to -1.\n\nThis causes the following warning on module unload:\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 1 PID: 963 at kernel/kthread.c:1430\n    kthread_destroy_worker+0x84/0x98\n  ...\n  vdec 30210000.video-codec: Runtime PM usage count underflow!","Type":"Description","Title":"media: chips-media: wave5: Fix PM runtime usage count underflow"}]}}}