Security readout for executives and security teams
Plain-English summary
A Linux AMD GPU driver flaw can mishandle synchronization-fence references during virtual-address updates. A low-privileged local process may trigger use-after-free behavior, potentially crashing the system. The CVSS assessment also allows broader confidentiality and integrity impact, but the supplied evidence specifically demonstrates refcount underflow, invalid memory access, and kernel panic.
Executive priority
Prioritize remediation for shared workstations, GPU compute hosts, and other systems permitting untrusted local workloads. The demonstrated outcome is a full system crash, while the CVSS assessment indicates possible broader compromise. Internet exposure alone does not establish reachability because the stated attack vector is local.
Technical view
The amdgpu_gem_va_ioctl path could select a dma_fence too early and manage its reference incorrectly. A stale or freed fence could later be used while updating GPU timelines. The correction selects the fence after VA mapping, safely acquires its reference, exports it to the timeline sync object, and then releases the local reference.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions with the AMDGPU driver in use. Exploitation requires local access with low privileges and no user interaction. The supplied affected-version data is unusual and incomplete for distribution kernels, so organizations should map vendor kernel packages to the referenced upstream fixes.
Exploitation context
The CVSS vector rates exploitation as local, low complexity, and requiring low privileges. The supplied crash trace confirms a reachable kernel use-after-free and denial-of-service condition. The CVE is not in KEV, and the source bundle provides no evidence of active exploitation or a public exploit.
Researcher notes
The strongest supplied evidence is a dma_fence lifetime error causing refcount underflow, use-after-free, page fault, and kernel panic during GPU timeline processing. No CWE, exploit report, or distribution-package mapping is supplied. Treat impacts beyond denial of service as CVSS-assessed potential, not demonstrated exploitation.
Mitigation direction
- Install a distribution kernel containing the applicable referenced stable fix.
- Check Linux distribution advisories for package-specific affected and corrected versions.
- Prioritize multi-user systems where untrusted local workloads can access AMD GPU devices.
- Restrict untrusted access to AMD GPU device interfaces where operationally feasible until patched.
Validation and detection
- Inventory Linux kernel package versions and systems using the AMDGPU driver.
- Map distribution patches against the three referenced upstream stable commits.
- Confirm the corrected kernel is running after installation and reboot.
- Review kernel logs for amdgpu refcount underflows, dma_fence faults, or unexplained panics.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2026-43237 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/e9e477d3197f7d8955a042c0d7f53f78f13218baCVE reference, Linux
- https://git.kernel.org/stable/c/0399b8416ecf64ef86ad23401fe23eabdb07831aCVE reference, Linux
- https://git.kernel.org/stable/c/bd8150a1b3370a9f7761c5814202a3fe5a79f44fCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.