{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54235 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2023-54235 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2023-54235 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-54235/ (Markdown: https://insights.sbomify.com/CVE-2023-54235/index.md)","id":"CVE-2023-54235","markdown":"https://insights.sbomify.com/CVE-2023-54235/index.md","name":"CVE-2023-54235","record":{"aliases":["BELL-CVE-2023-54235","DEBIAN-CVE-2023-54235","GHSA-68j8-v58c-g6h7","UBUNTU-CVE-2023-54235"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel PCI DOE driver can cause a kernel warning and potential denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/DOE: Fix destroy_work_on_stack() race\n\nThe following debug object splat was observed in testing:\n\n  ODEBUG: free active (active state 0) object: 0000000097d23782 object type: work_struct hint: doe_statemachine_work+0x0/0x510\n  WARNING: CPU: 1 PID: 71 at lib/debugobjects.c:514 debug_print_object+0x7d/0xb0\n  ...\n  Workqueue: pci 0000:36:00.0 DOE [1 doe_statemachine_work\n  RIP: 0010:debug_print_object+0x7d/0xb0\n  ...\n  Call Trace:\n   ? debug_print_object+0x7d/0xb0\n   ? __pfx_doe_statemachine_work+0x10/0x10\n   debug_object_free.part.0+0x11b/0x150\n   doe_statemachine_work+0x45e/0x510\n   process_one_work+0x1d4/0x3c0\n\nThis occurs because destroy_work_on_stack() was called after signaling\nthe completion in the calling thread.  This creates a race between\ndestroy_work_on_stack() and the task-\u003ework struct going out of scope in\npci_doe().\n\nSignal the work complete after destroying the work struct.  This is safe\nbecause signal_task_complete() is the final thing the work item does and\nthe workqueue code is careful not to access the work struct after.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"PCI/DOE: Fix destroy_work_on_stack() race","id":"CVE-2023-54235","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"net/net_failover: fix txq exceeding warning","id":"CVE-2023-54236"},"packages":[],"prev":{"headline":"scsi: mpi3mr: Fix missing mrioc-\u003eevtack_cmds initialization","id":"CVE-2023-54234"},"products":["Linux"],"published":"2025-12-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-23","vendors":["Linux"]},"summary":"A race condition in the Linux kernel PCI DOE driver can cause a kernel warning and potential denial of service.","url":"https://insights.sbomify.com/CVE-2023-54235/"}