Menu

Star on GitHub · 3.2k

CVE-2026-43237

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4 This commit simplifies the a…

Published May 6, 2026CWE-416EPSS 0.12%

Overview

CVE-2026-43237 is a high-severity vulnerability. It was published on May 6, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4

This commit simplifies the amdgpu_gem_va_ioctl function, key updates

include:

- Moved the logic for managing the last update fence directly into

amdgpu_gem_va_update_vm.

- Introduced checks for the timeline point to enable conditional

replacement or addition of fences.

v2: Addressed review comments from Christian.

v3: Updated comments (Christian).

v4: The previous version selected the fence too early and did not manage its

reference correctly, which could lead to stale or freed fences being used.

This resulted in refcount underflows and could crash when updating GPU

timelines.

The fence is now chosen only after the VA mapping work is completed, and its

reference is taken safely. After exporting it to the VM timeline syncobj, the

driver always drops its local fence reference, ensuring bal

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-43237?

CVE-2026-43237 is a high-severity vulnerability. It was published on May 6, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-43237?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-43237?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-43237?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-43237 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all