Linux Kernel up to 6.12.74/6.18.15/6.19.5 kernel/kthread.c wave5_vpu_timer_callback race condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.9$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.12.74/6.18.15/6.19.5. It has been rated as critical. Affected is the function wave5_vpu_timer_callback of the file kernel/kthread.c. The manipulation leads to race condition. This vulnerability is referenced as CVE-2026-43293. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.74/6.18.15/6.19.5 and classified as critical. This issue affects the function wave5_vpu_timer_callback of the file kernel/kthread.c. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix kthread worker destruction in polling mode Fix the cleanup order in polling mode (irq < 0) to prevent kernel warnings during module removal. Cancel the hrtimer before destroying the kthread worker to ensure work queues are empty. In polling mode, the driver uses hrtimer to periodically trigger wave5_vpu_timer_callback() which queues work via kthread_queue_work(). The kthread_destroy_worker() function validates that both work queues are empty with WARN_ON(!list_empty(&worker->work_list)) and WARN_ON(!list_empty(&worker->delayed_work_list)). The original code called kthread_destroy_worker() before hrtimer_cancel(), creating a race condition where the timer could fire during worker destruction and queue new work, triggering the WARN_ON. This causes the following warning on every module unload in polling mode: ------------[ cut here ]------------ WARNING: CPU: 2 PID: 1034 at kernel/kthread.c:1430 kthread_destroy_worker+0x84/0x98 Modules linked in: wave5(-) rpmsg_ctrl rpmsg_char ... Call trace: kthread_destroy_worker+0x84/0x98 wave5_vpu_remove+0xc8/0xe0 [wave5] platform_remove+0x30/0x58 ... ---[ end trace 0000000000000000 ]---

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-43293 since 05/01/2026. The exploitation is known to be difficult. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 6.12.75, 6.18.16 or 6.19.6 eliminates this vulnerability. Applying the patch 156020e889edf4593870d926d3c4a6d06baac44a/cc8071b1bac6568ea09d54be2d4f74dba80e17f8/0c2e752688a0ee3b89993e6de6c496d863870c93/5a0c122e834b2f7f029526422c71be922960bf03 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1454). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Red Hat Enterprise Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Microsoft Azure Linux
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.9

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.75/6.18.16/6.19.6
Patch: 156020e889edf4593870d926d3c4a6d06baac44a/cc8071b1bac6568ea09d54be2d4f74dba80e17f8/0c2e752688a0ee3b89993e6de6c496d863870c93/5a0c122e834b2f7f029526422c71be922960bf03

Timelineinfo

05/01/2026 CVE reserved
05/08/2026 +7 days Advisory disclosed
05/08/2026 +0 days VulDB entry created
06/15/2026 +38 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-43293 (🔒)
GCVE (CVE): GCVE-0-2026-43293
GCVE (VulDB): GCVE-100-362075
CERT Bund: WID-SEC-2026-1454 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 05/08/2026 16:09
Updated: 06/15/2026 18:07
Changes: 05/08/2026 16:09 (59), 05/18/2026 00:54 (11), 06/15/2026 18:07 (7)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!