CVE-2026-93070

Local kernel compromise via IPU6 double free

Published Sep 17, 2026 · Updated Sep 18, 2026

Double free in the Linux IPU6 media driver allows local users to corrupt kernel memory during automatic device initialization. The isys and psys error paths release the auxiliary device, whose ipu6_bus_release callback frees pdata, and then call kfree on the same pdata again. An Intel IPU6 PCI device and an initialization failure are required; ordinary local memory pressure can trigger the failure without user interaction, leading to kernel disclosure, arbitrary writes, or panic.

CVSS severity7.8
High
EPSS probability0.16%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Double free in the Linux IPU6 media driver allows local users to corrupt kernel memory during automatic device initialization. The isys and psys error paths release the auxiliary device, whose ipu6_bus_release callback frees pdata, and then call kfree on the same pdata again. An Intel IPU6 PCI device and an initialization failure are required; ordinary local memory pressure can trigger the failure without user interaction, leading to kernel disclosure, arbitrary writes, or panic.

The record

CVE
CVE-2026-93070
Published
Sep 17, 2026
Updated
Sep 18, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-415, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.10
  2. Affected versionversion=cb3117b074aefb0320d8d728a0a7f277a121adbd <5323ed5a7bb2568191ec676b2035b0396105aa05
  3. Affected versionversion=cb3117b074aefb0320d8d728a0a7f277a121adbd <7d102d1f0631807a491a140f67c9628dea85dfd2
  4. Affected versionversion=cb3117b074aefb0320d8d728a0a7f277a121adbd <9be07216af4cfc4813e1a46ce26407d31ea845de
  5. Affected versionversion=cb3117b074aefb0320d8d728a0a7f277a121adbd <faa1eb97f0e66bf122f44b62be6b323f86333e9f

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.10; version=cb3117b074aefb0320d8d728a0a7f277a121adbd <5323ed5a7bb2568191ec676b2035b0396105aa05; version=cb3117b074aefb0320d8d728a0a7f277a121adbd <7d102d1f0631807a491a140f67c9628dea85dfd2; version=cb3117b074aefb0320d8d728a0a7f277a121adbd <9be07216af4cfc4813e1a46ce26407d31ea845de; version=cb3117b074aefb0320d8d728a0a7f277a121adbd <faa1eb97f0e66bf122f44b62be6b323f86333e9f

Published CVSS scores

7.8Linux CNACVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-415Double Free
T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started