Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 2a0e0f4773fe8032fb17e56f897bee32ce3cdc2b – < d96799ee3b78962c80e4b6653734f488f999ca09
    • affected abf04be0e7071f2bcd39bf97ba407e7d4439785e – < c4f9c0a3a6df143f2e1092823b7fa9e07d6ab57f
    • affected abf04be0e7071f2bcd39bf97ba407e7d4439785e – < 19cf3ba16dcc2ef059dcf010072d4f96d76486e0
    • affected abf04be0e7071f2bcd39bf97ba407e7d4439785e – < e3a3a097eaebaf234a482b4d2f9f18fe989208c1
    • affected 95628b830952943631d3d74f73f431f501c5d6f5
    • affected 6.1.24 – < 6.1.53
    • affected 6.2.11 – < 6.3
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.1.53 – ≤ 6.1.*
    • unaffected 6.4.16 – ≤ 6.4.*
    • unaffected 6.5.3 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54235 badge
[![CVE-2023-54235](https://cveledger.app/badge/CVE-2023-54235.svg)](https://cveledger.app/cve/CVE-2023-54235)

Record last updated .