CVE-2026-43237·Kernel vulnerability
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 balanced refcounting and avoiding use-after-free on dma_fence. Crash signature: [ 205.828135] refcount_t: underflow; use-after-free. [ 205.832963] WARNING: CPU: 30 PID: 7274 at lib/refcount.c:28 refcount_warn_saturate+0xbe/0x110 ... [ 206.074014] Call Trace: [ 206.076488] <TASK> [ 206.078608] amdgpu_gem_va_ioctl+0x6ea/0x740 [amdgpu] [ 206.084040] ? __pfx_amdgpu_gem_va_ioctl+0x10/0x10 [amdgpu] [ 206.089994] drm_ioctl_kernel+0x86/0xe0 [drm] [ 206.094415] drm_ioctl+0x26e/0x520 [drm] [ 206.098424] ? __pfx_amdgpu_gem_va_ioctl+0x10/0x10 [amdgpu] [ 206.104402] amdgpu_drm_ioctl+0x4b/0x80 [amdgpu] [ 206.109387] __x64_sys_ioctl+0x96/0xe0 [ 206.113156] do_syscall_64+0x66/0x2d0 ... [ 206.553351] BUG: unable to handle page fault for address: ffffffffc0dfde90 ... [ 206.553378] RIP: 0010:dma_fence_signal_timestamp_locked+0x39/0xe0 ... [ 206.553405] Call Trace: [ 206.553409] <IRQ> [ 206.553415] ? __pfx_drm_sched_fence_free_rcu+0x10/0x10 [gpu_sched] [ 206.553424] dma_fence_signal+0x30/0x60 [ 206.553427] drm_sched_job_done.isra.0+0x123/0x150 [gpu_sched] [ 206.553434] dma_fence_signal_timestamp_locked+0x6e/0xe0 [ 206.553437] dma_fence_signal+0x30/0x60 [ 206.553441] amdgpu_fence_process+0xd8/0x150 [amdgpu] [ 206.553854] sdma_v4_0_process_trap_irq+0x97/0xb0 [amdgpu] [ 206.554353] edac_mce_amd(E) ee1004(E) [ 206.554270] amdgpu_irq_dispatch+0x150/0x230 [amdgpu] [ 206.554702] amdgpu_ih_process+0x6a/0x180 [amdgpu] [ 206.555101] amdgpu_irq_handler+0x23/0x60 [amdgpu] [ 206.555500] __handle_irq_event_percpu+0x4a/0x1c0 [ 206.555506] handle_irq_event+0x38/0x80 [ 206.555509] handle_edge_irq+0x92/0x1e0 [ 206.555513] __common_interrupt+0x3e/0xb0 [ 206.555519] common_interrupt+0x80/0xa0 [ 206.555525] </IRQ> [ 206.555527] <TASK> ... [ 206.555650] RIP: 0010:dma_fence_signal_timestamp_locked+0x39/0xe0 ... [ 206.555667] Kernel panic - not syncing: Fatal exception in interrupt
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.19.6
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.12% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-43237 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.12%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.6
Fixed in: 6.19.6
How to fix this CVE
Update your Linux kernel to version 6.19.6 or later to resolve a critical fence reference counting vulnerability in the AMD GPU driver. This vulnerability can cause kernel panics and system crashes when GPU virtual address mappings are updated. Apply the update immediately and reboot your system to ensure the fix is active.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version with `uname -r`. If it shows 6.19.0 through 6.19.5, you are vulnerable.
- Step 2: Verify if AMD GPU drivers are in use by running `lspci | grep -i amd` and checking for AMD graphics devices.
- Step 3: Search kernel logs for refcount underflow warnings using `sudo dmesg | grep -i 'refcount_t: underflow'` or `sudo journalctl -xe | grep -i 'refcount'`.
- Step 4: After patching, confirm the kernel version with `uname -r` shows 6.19.6 or newer, then verify no new refcount errors appear in logs after a full GPU workload cycle.
FAQ
What is CVE-2026-43237?
CVE-2026-43237 is a use-after-free vulnerability in the Linux kernel's AMD GPU driver that occurs during virtual address mapping updates. Improper fence reference counting can cause the kernel to access freed memory, triggering refcount underflows and kernel panics when GPU timeline synchronization objects are managed.
Is CVE-2026-43237 being actively exploited?
No, CVE-2026-43237 is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, it can be triggered by local applications performing GPU operations, making it a denial-of-service risk in multi-tenant environments.
What versions of Kernel are affected by CVE-2026-43237?
Linux kernel versions 6.19 through 6.19.5 are vulnerable. The fix is included in kernel 6.19.6 and all subsequent releases.
How do I check if my server is vulnerable to CVE-2026-43237?
Run `uname -r` to check your kernel version. If it reports 6.19.0 through 6.19.5 and AMD GPU devices are present (check with `lspci | grep -i amd`), your system is vulnerable.
Does Defensia detect CVE-2026-43237?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-43237 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-43237. Free for 1 server.
Get started free