media: chips-media: wave5: Fix PM runtime usage count underflow
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!
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.16, 6.19.6
- CVEs
- CVE-2026-43301
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:01 UTC · Revision 1
Source evidence
media: chips-media: wave5: Fix PM runtime usage count underflow
core-osv · Original sourcePublished 8 May 2026, 13:11 UTC
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!
osv:CVE-2026-43301
Kernel
Fixed versions: 6.18.16, 6.19.6
Complete source record
{
"id": "ed8f45a5be99d3ed6480136bbc67215eda6ceabf3f437730f7c7e3a0bff047ae",
"url": "https://osv.dev/vulnerability/CVE-2026-43301",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "media: chips-media: wave5: Fix PM runtime usage count underflow",
"summary": "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!",
"evidence": "osv:CVE-2026-43301",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.16",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-43301",
"aliases": [
"CVE-2026-43301"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "9707a6254a8a6b978bde811a44fe07d86c229d1c"
},
{
"fixed": "3a278a55ead50db2444c8f01410c7f5a68723990"
},
{
"fixed": "0bffda02317989f8d5cdc2d4462a4110b1290cf0"
},
{
"fixed": "9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43301.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.8.0"
},
{
"fixed": "6.18.16"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43301.json"
}
}
],
"modified": "2026-10-28T02:30:22.763113876Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0bffda02317989f8d5cdc2d4462a4110b1290cf0",
"https://git.kernel.org/stable/c/3a278a55ead50db2444c8f01410c7f5a68723990",
"https://git.kernel.org/stable/c/9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43301.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-43301",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43301.json"
}
},
"related_cves": [
{
"value": "CVE-2026-43301",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 488912,
"published_at": "2026-05-08T13:11:22.234+00:00"
}