CVE-2026-74357 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux systems with the amdgpu driver should assess exposure and apply patches or mitigations as needed. They should review and apply the provided kernel patches to fix the vulnerability, monitor Linux kernel updates for potential backports of the fix, and consider implementing additional monitoring and logging to detect potential exploitation attempts.

Why it matters

This vulnerability in the Linux kernel's amdgpu_coredump ring dump functionality could lead to a denial of service or potential elevation of privileges. Linux kernel developers, maintainers, and users of Linux systems with the amdgpu driver should assess exposure and apply patches or mitigations as needed.

• Potential denial of service (DoS) due to slab-out-of-bounds write
• Possible elevation of privileges through exploitation of the vulnerability
• Increased risk of system crashes or instability
• Need for verification of affected versions and application of patches

Technical summary

The vulnerability exists in the amdgpu_coredump functionality of the Linux kernel. A race condition between two loops iterating over device rings can lead to a slab-out-of-bounds write. This occurs when the fence state changes between the counting and copying loops, causing the index to exceed the allocated ring count. The vulnerability was found during IGT stressful testing with the amd_queue_reset test, specifically the OVERSIZE subtest. A KASAN log was provided, detailing a slab-out-of-bounds write of size 4 at address ffff888106154258. The issue affects Linux kernel developers, Linux distribution maintainers, and users of Linux systems with the amdgpu driver.

Defensive priority

Medium

Recommended defensive actions

• Review and apply the provided kernel patches to fix the vulnerability
• Monitor Linux kernel updates for potential backports of the fix
• Consider implementing additional monitoring and logging to detect potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability was found during IGT stressful testing with the amd_queue_reset test, specifically the OVERSIZE subtest. A KASAN log was provided, detailing a slab-out-of-bounds write of size 4 at address ffff888106154258.

Sources and references

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.