# CVE-2026-99058: workqueue: Fix NULL current_pwq deref in chained work check


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110945, BELL-CVE-2026-99058, DEBIAN-CVE-2026-99058, GHSA-vhm2-x82m-jxjm, UBUNTU-CVE-2026-99058

## What is CVE-2026-99058?

CVE-2026-99058 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official 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.

## Which versions are affected by CVE-2026-99058?


## How do I fix CVE-2026-99058?

Upgrade to a fixed version.

## Is CVE-2026-99058 being exploited?

There is no known exploitation of CVE-2026-99058 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99058 and fix it if it is affected.

What it is: CVE-2026-99058 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99058 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99058/ (Markdown: https://insights.sbomify.com/CVE-2026-99058/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99058
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99058
- OSV: https://osv.dev/vulnerability/CVE-2026-99058

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99058/
Summaries are generated and may contain mistakes; the official description above is the record.