# CVE-2023-54235: PCI/DOE: Fix destroy_work_on_stack() race

> A race condition in the Linux kernel PCI DOE driver can cause a kernel warning and potential denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 23 May 2026
- **Also known as:** BELL-CVE-2023-54235, DEBIAN-CVE-2023-54235, GHSA-68j8-v58c-g6h7, UBUNTU-CVE-2023-54235

## What is CVE-2023-54235?

CVE-2023-54235 is a vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

PCI/DOE: Fix destroy_work_on_stack() race

The following debug object splat was observed in testing:

  ODEBUG: free active (active state 0) object: 0000000097d23782 object type: work_struct hint: doe_statemachine_work+0x0/0x510
  WARNING: CPU: 1 PID: 71 at lib/debugobjects.c:514 debug_print_object+0x7d/0xb0
  ...
  Workqueue: pci 0000:36:00.0 DOE [1 doe_statemachine_work
  RIP: 0010:debug_print_object+0x7d/0xb0
  ...
  Call Trace:
   ? debug_print_object+0x7d/0xb0
   ? __pfx_doe_statemachine_work+0x10/0x10
   debug_object_free.part.0+0x11b/0x150
   doe_statemachine_work+0x45e/0x510
   process_one_work+0x1d4/0x3c0

This occurs because destroy_work_on_stack() was called after signaling
the completion in the calling thread.  This creates a race between
destroy_work_on_stack() and the task->work struct going out of scope in
pci_doe().

Signal the work complete after destroying the work struct.  This is safe
because signal_task_complete() is the final thing the work item does and
the workqueue code is careful not to access the work struct after.

## Which versions are affected by CVE-2023-54235?


## How do I fix CVE-2023-54235?

Apply the vendor's patch.

## Is CVE-2023-54235 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54235 and fix it if it is affected.

What it is: CVE-2023-54235 is a vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54235 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-2023-54235/ (Markdown: https://insights.sbomify.com/CVE-2023-54235/index.md)
```

## Sources

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

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