Security readout for executives and security teams
Plain-English summary
A race during removal of a Linux accel/ivpu device can let recovery work access resources after they are freed. This use-after-free may crash the system or potentially compromise data and system integrity. Exploitation requires local, low-privileged access according to the CVSS vector.
Executive priority
Treat this as a high-priority local privilege boundary issue on systems using accel/ivpu, especially shared or multi-user hosts. Patch through supported kernel channels promptly. Systems without this driver or relevant hardware likely have lower practical exposure, but applicability should be verified rather than assumed.
Technical view
During ivpu_dev_fini(), cancel_work_sync() stopped existing recovery work but did not prevent new work from being queued. Recovery could then access freed resources. The stable fix uses disable_work_sync() and renames ivpu_pm_cancel_recovery() to ivpu_pm_disable_recovery(), preventing recovery scheduling after removal begins.
Likely exposure
Exposure is limited to systems running affected Linux kernel builds where accel/ivpu is present and device removal can overlap recovery activity. The supplied record lists 6.8, 6.12.46, 6.16.6, and 6.17 as affected entries, but does not fully explain version-range semantics or distribution backports.
Exploitation context
The CVSS 3.1 score is 7.8 with local access and low privileges required, no user interaction, and potentially high confidentiality, integrity, and availability impact. The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The central condition is a workqueue lifecycle race: cancellation handled queued or running recovery work but did not disable future submissions during teardown. The cited commits are authoritative fix references. The bundle does not establish exploit reliability, affected distribution packages, required hardware state, or exact fixed release boundaries.
Mitigation direction
- Update to a vendor-supported kernel containing the applicable referenced stable fix.
- Check distribution advisories because vendors may backport fixes without changing the apparent kernel version.
- Prioritize systems exposing accel/ivpu functionality to untrusted local users.
- If updating is delayed, obtain vendor-approved guidance for limiting accel/ivpu exposure.
Validation and detection
- Inventory kernel build identifiers and determine whether accel/ivpu is present on each system.
- Compare vendor kernel changelogs against the three referenced stable commits.
- Confirm the source includes disable_work_sync() in the ivpu device-finalization path.
- After updating, verify the running kernel matches the installed fixed package.
- Review relevant system logs for crashes associated with ivpu recovery or device removal.
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.
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-39896 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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability 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
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.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/54c49eca38dbd06913a696f6d7610937dcfad226CVE reference, Linux
- https://git.kernel.org/stable/c/565d2c15b6c36c3250e694f7b9a86229c1787be5CVE reference, Linux
- https://git.kernel.org/stable/c/69a79ada8eb034ce016b5b78fb7d08d8687223deCVE 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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.