PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-43170 Linux CVE debrief

A Linux kernel vulnerability, CVE-2026-43170, has been resolved, which could lead to a kernel panic when dwc3_gadget_vbus_draw() is called from atomic context. The issue arises because some power-supply-core APIs invoked by dwc3_gadget_vbus_draw() may sleep, causing a kernel panic. The fix involves moving vbus_draw into a workqueue context. This change helps prevent kernel panics by ensuring that operations that may sleep are executed in a suitable context. Linux kernel developers, maintainers, and users should assess exposure and apply patches to prevent potential kernel panics. The vulnerability has a CVSS score of 5.5, indicating medium severity.

Vendor
Linux
Product
Unknown
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-06
Original CVE updated
2026-10-30
Advisory published
2026-05-06
Advisory updated
2026-10-30

Who should care

Linux kernel developers, maintainers, and users who need to assess exposure and apply patches to prevent potential kernel panics. The vulnerability affects systems using the Linux kernel, particularly those with versions within the vulnerable ranges. Operators, platform administrators, and security teams should review the vulnerability details and take necessary actions to mitigate potential risks. This includes verifying Linux kernel versions, applying, 6

Why it matters

CVE-2026-43170 is a medium-severity vulnerability in the Linux kernel that requires verification of exposure, patch application, and monitoring to prevent system instability.

  • Verification of Linux kernel versions and exposure assessment is required to prevent potential system instability.
  • Patch application is necessary to prevent kernel panics in systems using the affected Linux kernel versions.
  • Monitoring system logs for kernel panic events related to dwc3_gadget_vbus_draw() can help detect potential issues.

Technical summary

The Linux kernel vulnerability CVE-2026-43170 is caused by dwc3_gadget_vbus_draw() being called from atomic context, leading to potential kernel panics due to sleeping operations in power-supply-core APIs. The fix moves vbus_draw into a workqueue context, preventing kernel panics by ensuring that operations that may sleep are executed in a suitable context. This change is crucial for systems using the affected Linux kernel versions, as it helps maintain system stability and prevent potential crashes. Linux kernel developers, maintainers, and users should prioritize assessing exposure and applying patches.

Defensive priority

Medium priority should be given to assessing exposure and applying patches, as the vulnerability has a CVSS score of 5.5 and is related to a critical system component.

Recommended defensive actions

  • Assess exposure by checking if the Linux kernel versions in use fall within the vulnerable ranges (5.13 to 6.6.128, 6.7 to 6.12.75, 6.13 to 6.18.16, 6.19 to 6.19.6).
  • Apply patches from the Linux kernel stable repository as referenced in the source references.
  • Monitor system logs for potential kernel panic events related to dwc3_gadget_vbus_draw().
  • Verify the effectiveness of the patches in preventing kernel panics in a controlled environment.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, its impact, and the fix. However, the corpus does not establish specific versions affected or exploitation instances. The vulnerability is in the Linux kernel, specifically in the dwc3 gadget driver. The fix moves the vbus_draw operation into a workqueue context to prevent kernel panics caused by sleeping operations in power-supply-core APIs. Defenders should verify Linux kernel versions in use, assess exposure, and apply patches from the Linux kernel stable as a

Sources and references

Verified primary and authoritative sources

  • CVE-2026-43170 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-43170

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-43170 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-43170

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/2333653ef854c2cc124077f71a8526f03bf6e06a

    416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/54aaa3b387c2f580a99dc86a9cc2eb6dfaf599a7

    416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/74a231e3d99d310497ab0ccb359539a6063b316a

    416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/76c1123ffccfaba95cf4ecc2a50f95504a522424

    416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a7a80c25b65112768eeba58a7af129d3c52a6d90

    416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b214f0b11a0f1186f83c284f6a545110f76066b6

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.