CVE-2023-54235

Kernel warning via PCI work lifetime race

Published Dec 30, 2025 · Updated Dec 30, 2025

A lifetime race in Linux kernel 6.3 PCI/DOE handling allows attackers to trigger a kernel warning during DOE task completion. In pci_doe(), the worker signals completion before destroy_work_on_stack() retires task->work, allowing the caller's stack object to leave scope while cleanup still uses it. The path requires PCI/DOE activity; the observed consequence is an active-work debug warning, while a crash depends on warning-panic configuration.

CVSS severityUnavailable
Unscored
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

A lifetime race in Linux kernel 6.3 PCI/DOE handling allows attackers to trigger a kernel warning during DOE task completion. In pci_doe(), the worker signals completion before destroy_work_on_stack() retires task->work, allowing the caller's stack object to leave scope while cleanup still uses it. The path requires PCI/DOE activity; the observed consequence is an active-work debug warning, while a crash depends on warning-panic configuration.

The record

CVE
CVE-2023-54235
Published
Dec 30, 2025
Updated
Dec 30, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Dec 30, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 30, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2a0e0f4773fe8032fb17e56f897bee32ce3cdc2b <d96799ee3b78962c80e4b6653734f488f999ca09
  2. Affected versionversion=6.3
  3. Affected versionversion=95628b830952943631d3d74f73f431f501c5d6f5
  4. Affected versionversion=abf04be0e7071f2bcd39bf97ba407e7d4439785e <19cf3ba16dcc2ef059dcf010072d4f96d76486e0
  5. Affected versionversion=abf04be0e7071f2bcd39bf97ba407e7d4439785e <c4f9c0a3a6df143f2e1092823b7fa9e07d6ab57f
  6. Affected versionversion=abf04be0e7071f2bcd39bf97ba407e7d4439785e <e3a3a097eaebaf234a482b4d2f9f18fe989208c1

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=2a0e0f4773fe8032fb17e56f897bee32ce3cdc2b <d96799ee3b78962c80e4b6653734f488f999ca09; version=6.3; version=95628b830952943631d3d74f73f431f501c5d6f5; version=abf04be0e7071f2bcd39bf97ba407e7d4439785e <19cf3ba16dcc2ef059dcf010072d4f96d76486e0; version=abf04be0e7071f2bcd39bf97ba407e7d4439785e <c4f9c0a3a6df143f2e1092823b7fa9e07d6ab57f; version=abf04be0e7071f2bcd39bf97ba407e7d4439785e <e3a3a097eaebaf234a482b4d2f9f18fe989208c1

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo