CVE-2026-99058

UnknownEPSS 0.18%

Last modified

CVE-2026-99058 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in chained work check current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function. is_chained_work() can be reached while queueing on a draining or destroying workqueue. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in chained work check current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function. is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker->current_pwq is NULL, and the chained-work test can fault before it emits the intended warning. Guard the chained-work test with worker->current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.

Metrics

EPSS Probability
0.18%

7.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 8d03ecfe471802d6afe97da97722b6924533aa82, < 73bec442f913855907b63225306dd162c18e5c71; >= 8d03ecfe471802d6afe97da97722b6924533aa82, < 6877de2c75f0dd342099a1357856e6c8d474abc3; >= 8d03ecfe471802d6afe97da97722b6924533aa82, < 54361e4924c2c52a501b74ef10217c32f45fccfa; >= 8d03ecfe471802d6afe97da97722b6924533aa82, < 3dc61af2998cfc7312d6e59bbdcd5eed074483f2; >= 8d03ecfe471802d6afe97da97722b6924533aa82, < 729d576df89c7e4341e58c452f8890620a610ac2; >= 8d03ecfe471802d6afe97da97722b6924533aa82, < b12a25fb2b9d5dac80e419d695450cc17a51fdfd; >= 8d03ecfe471802d6afe97da97722b6924533aa82, < 1a2668682e998039a027796b236319b380078a6a; >= 8d03ecfe471802d6afe97da97722b6924533aa82, < 980db94e3eeefdd8a1c46f86412c33a7f7806f51
LinuxLinux3.9

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-99058?
In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in chained work check current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function. is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker->current_pwq is NULL, and the chained-work test can fault before it emits the intended warning. Guard the chained-work test with worker->current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.
How severe is CVE-2026-99058?
Severity scoring for CVE-2026-99058 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-99058?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-99058?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST