Security readout for executives and security teams
Plain-English summary
A race condition in the Linux ivpu accelerator driver can leave buffer objects incompletely unmapped during context shutdown. The supplied CVSS assessment indicates a low-privileged local user could potentially cause serious confidentiality, integrity, and availability impacts. However, the technical description documents a teardown warning and does not explain a demonstrated security impact.
Executive priority
Treat this as high priority where untrusted local users share systems exposing ivpu. Patch through normal emergency kernel maintenance after vendor confirmation. Systems without the driver or without relevant local access are lower urgency, but the supplied data is insufficient to declare them unaffected solely by version.
Technical view
ivpu_gem_bo_free() could remove a buffer object from the tracking list before unmapping completed. Concurrent file_priv_unbind() teardown could then reach drm_mm_takedown() with an unclean memory manager. The upstream correction holds bo_list_lock across unmapping and list removal, ensuring teardown either sees a fully unmapped object or can unmap the still-listed object.
Likely exposure
Exposure requires Linux systems running an affected kernel with the accel/ivpu driver and a local low-privileged attack path. The bundle names versions including 6.8, 6.12.68, 6.17.13, 6.18.2, and 6.19, but its version data is ambiguous. Confirm exact affected and fixed releases through kernel or distribution guidance.
Exploitation context
The supplied CVSS vector requires local access and low privileges, with no user interaction. The bundle reports no CISA KEV listing and provides no evidence of active exploitation or a public proof of concept. It also does not establish whether the warning is reliably exploitable beyond incorrect teardown behavior.
Researcher notes
The documented defect is a locking and object-lifecycle race during buffer-object unbinding. The fix serializes unmapping with bo_list_lock. CVSS claims complete confidentiality, integrity, and availability impact, but the source description only identifies an unclean memory-manager warning; the causal path to those security impacts is not documented in the bundle.
Mitigation direction
- Update to a vendor-supported kernel containing the applicable referenced stable fix.
- Check Linux distribution advisories for exact affected and corrected package versions.
- Prioritize multi-user systems where untrusted local users can access the ivpu device.
- Restrict unnecessary local access to accelerator devices until updates are applied.
Validation and detection
- Record the running kernel and distribution package versions on systems using ivpu.
- Confirm whether the ivpu driver is present, loaded, and accessible to untrusted users.
- Match kernel builds against vendor advisories or the referenced stable commits.
- After updating, verify the corrected kernel is running and monitor teardown warnings.
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-2025-68749 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/0328bb097bef05a796217c54b3d651cc3782827cCVE reference, Linux
- https://git.kernel.org/stable/c/fb16493ebd8f171bcf0772262619618a131f30f7CVE reference, Linux
- https://git.kernel.org/stable/c/d71333ffdd3707d84cfb95acfaf8ba892adc066bCVE reference, Linux
- https://git.kernel.org/stable/c/00812636df370bedf4e44a0c81b86ea96bca8628CVE 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.