In the Linux kernel, the following vulnerability has been resolved:
accel/ivpu: Disallow re-exporting imported GEM objects
Prevent re-exporting of imported GEM buffers by adding a custom
prime_handle_to_fd callback that checks if the object is imported
and returns -EOPNOTSUPP if so.
Re-exporting imported GEM buffers causes loss of buffer flags settings,
leading to incorrect device access and data corruption.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s ivpu accelerator driver can corrupt data when an already imported graphics buffer is exported again. A local, low-privileged user could potentially trigger incorrect device access without user interaction, affecting confidentiality, integrity, and availability. Network-based exploitation is not indicated.
Executive priority
Prioritize affected shared, multi-user, or untrusted-workload systems because exploitation requires local low-privileged access and could cause data exposure, modification, or disruption. Patch through normal emergency change controls after confirming vendor applicability; isolated systems without ivpu usage are lower priority.
Technical view
The ivpu GEM PRIME path allowed imported GEM objects to be re-exported. This loses buffer flag settings and may cause incorrect device access and data corruption. The kernel fix adds a custom handle-to-file-descriptor callback that rejects re-export of imported objects with EOPNOTSUPP.
Likely exposure
Exposure requires a Linux system using the affected ivpu driver and workflows that import then re-export GEM buffers. The record lists Linux 6.19, 7.0.7, and 7.1 as affected, but its version data is incomplete or ambiguous; confirm exact distribution kernel status with the vendor.
Exploitation context
CVSS 3.1 is 7.8: local access, low complexity, low privileges, and no user interaction, with potentially high confidentiality, integrity, and availability impact. The supplied record says KEV is false and provides no evidence of active exploitation or a public exploit.
Researcher notes
The security boundary failure is preservation of GEM buffer metadata across PRIME import and export. The fix blocks the unsafe transition rather than reconstructing lost flags. The supplied sources do not identify affected hardware models, attack prerequisites beyond CVSS, observed exploitation, or distribution-specific fixed package versions.
Mitigation direction
Install a vendor kernel containing the applicable upstream stable fix.
Confirm the selected kernel branch includes one of the referenced corrective commits.
Until patched, restrict untrusted local access to systems exposing the ivpu device.
Check distribution security guidance for backported fixes and precise affected versions.
Validation and detection
Inventory systems loading or packaging the Linux ivpu driver.
Record kernel and distribution package versions on potentially exposed systems.
Verify the installed kernel contains the branch-appropriate referenced fix.
Retest legitimate GEM import workflows and confirm imported objects cannot be re-exported.
Monitor kernel and device logs for ivpu access errors or unexplained data corruption.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CVE-2026-43498 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
We 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.