{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-16148 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-16148 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-16148 is a medium-severity vulnerability in zephyrproject zephyr, published on 14 Sep 2026. 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-2026-16148 and fix it if it is affected.\n\nWhat it is: CVE-2026-16148 is a medium-severity vulnerability in zephyrproject zephyr, published on 14 Sep 2026. 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-2026-16148 in the wild and no public exploit code.\n\nAffected product: zephyrproject zephyr. 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-2026-16148/ (Markdown: https://insights.sbomify.com/CVE-2026-16148/index.md)","id":"CVE-2026-16148","markdown":"https://insights.sbomify.com/CVE-2026-16148/index.md","name":"CVE-2026-16148","record":{"aliases":["GHSA-fvp9-j2pq-477x"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Zephyr RTOS kernel","requires_auth":"none","summary":"An attacker with physical USB access can cause a kernel panic in Zephyr RTOS by triggering a race condition during USB device controller re-initialization.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zephyr","cpe":[],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-666","name":"Operation on Resource in Wrong Phase of Lifetime"}],"description":"The ITE it82xx2 USB device-controller driver initialized its bus-suspend detection work with k_work_init_delayable(\u0026priv-\u003esuspended_work, suspended_handler) inside it82xx2_enable() (the driver's .enable op) in drivers/usb/udc/udc_it82xx2.c. This work item is scheduled essentially continuously while the USB bus is active: the interrupt handler reschedules it on every SOF frame and suspended_handler() reschedules itself, so its timeout node is normally linked in the kernel timeout list / a workqueue pending queue.\n\nk_work_init_delayable() (kernel/work.c) unconditionally overwrites the entire k_work_delayable structure, including its timeout and queue linkage, with no busy check. Because it82xx2_disable() does not cancel the work, a normal disable-then-enable cycle re-runs api-\u003eenable() (udc_enable() only rejects a redundant enable, not a re-enable after disable) and re-initializes the still-pending work in place, corrupting the kernel timeout/workqueue linked lists and causing a kernel panic.\n\nAn external USB host — for example a host performing USB DFU detach (dfu-util --detach) or forcing repeated attach/reset/re-enumeration — drives the udc_disable()/udc_enable() transitions and controls suspend/resume timing, so it can arrange for the suspend work to be pending across a re-enable. This yields an unauthenticated denial of service (kernel panic) reachable across the USB boundary from a removable, physically-connected host, with no confidentiality or integrity impact demonstrated.\n\nThe fix moves the k_work_init_delayable() call into the one-time preinit function so the work is initialized exactly once, eliminating the re-initialization of an in-use item.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Kernel panic in the it82xx2 USB device controller driver via re-initialization of a busy delayable work item","id":"CVE-2026-16148","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in Security Hardener","id":"CVE-2026-16149"},"packages":[],"prev":{"headline":"it82xx2 USB device controller submits incomplete OUT transfer buffers, causing use-after-free and event-list corruption","id":"CVE-2026-16147"},"products":["zephyr"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["zephyrproject"]},"summary":"An attacker with physical USB access can cause a kernel panic in Zephyr RTOS by triggering a race condition during USB device controller re-initialization.","url":"https://insights.sbomify.com/CVE-2026-16148/"}