PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-72075 Linux CVE debrief

A race condition vulnerability was found in the ims_pcu_reset_device sysfs callback in the Linux kernel. The ims_pcu_reset_device callback calls ims_pcu_execute_command without acquiring the pcu->cmd_mutex, leading to potential data races and corruption of the shared command buffer. This vulnerability could result in data races and corruption of the shared command buffer if triggered concurrently with other commands. The ims_pcu_reset_device callback in the Linux kernel does not acquire the pcu->cmd_mutex before calling ims_pcu_execute_command, potentially leading to data races and corruption of the shared command buffer. Defenders should verify patch application, review Linux kernel configurations, and monitor system logs for potential issues.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-15
Original CVE updated
2026-08-27
Advisory published
2026-08-15
Advisory updated
2026-08-27

Who should care

Linux kernel developers and maintainers, Linux distribution vendors, and users of Linux-based systems, especially those using the ims-pcu module, should be aware of this vulnerability and take necessary actions to mitigate it.

Technical summary

The ims_pcu_reset_device sysfs callback in the Linux kernel does not acquire the pcu->cmd_mutex before calling ims_pcu_execute_command, leading to a potential race condition vulnerability. This vulnerability could result in data races and corruption of the shared command buffer if triggered concurrently with other commands. The ims_pcu_reset_device callback calls ims_pcu_execute_command without acquiring the pcu->cmd_mutex, leading to potential data races and corruption of the shared command buffer. Acquiring the pcu->cmd_mutex before calling ims_pcu_execute_command can prevent data races and corruption of the shared command buffer.

Defensive priority

Medium

Recommended defensive actions

  • Verify and apply the patch to acquire pcu->cmd_mutex before calling ims_pcu_execute_command
  • Review and update Linux kernel configurations to ensure the ims-pcu module is properly configured
  • Monitor system logs for potential data races and corruption of the shared command buffer
  • Perform a thorough review of the Linux kernel code to identify potential similar vulnerabilities
  • Implement compensating controls for exposed systems while remediation is scheduled and verified
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Review relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further analysis and verification are needed to fully understand the issue. The ims_pcu_reset_device sysfs callback in the Linux kernel does not acquire the pcu->cmd_mutex before calling ims_pcu_execute_command, potentially leading to data races and corruption of the shared command buffer. Defenders should verify patch application, review Linux kernel configurations, and monitor system logs for potential issues.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-72075 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-72075 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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/025955847e1500ced4719ac178beff6a3b2f0e3c

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

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0fb84b1a3cdc74c453abc5f961c7d318c267ea4c

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

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/129187ec3f868829f61f6f07381ca72fe642d0b7

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

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/411b8c4b274737c3bf08e1e025801161603cfffc

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

  • Source reference

    Unverified legacy reference

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

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

  • Source reference

    Unverified legacy reference

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

    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.