CVE-2026-68330

Silent NPU response corruption via stale DMA cache

Published Aug 10, 2026 · Updated Aug 10, 2026

Incorrect DMA synchronization in the Linux kernel 6.16 allows stale Airoha NPU response data to be consumed on affected hardware. airoha_npu_send_msg() maps bidirectional mailbox traffic as DMA_TO_DEVICE, so unmapping does not invalidate CPU cache lines containing NPU-written responses. The timing-sensitive condition is limited to non-cache-coherent hardware such as EN7581; affected callers can silently consume stale WLAN or PPE data, but attackers cannot reliably invoke or influence the condition.

CVSS severity7.8
High
EPSS probability0.16%
Next 30 days · Sep 16, 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.

Book a demo

Summary

What happened

Incorrect DMA synchronization in the Linux kernel 6.16 allows stale Airoha NPU response data to be consumed on affected hardware. airoha_npu_send_msg() maps bidirectional mailbox traffic as DMA_TO_DEVICE, so unmapping does not invalidate CPU cache lines containing NPU-written responses. The timing-sensitive condition is limited to non-cache-coherent hardware such as EN7581; affected callers can silently consume stale WLAN or PPE data, but attackers cannot reliably invoke or influence the condition.

The record

CVE
CVE-2026-68330
Published
Aug 10, 2026
Updated
Aug 10, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 10, 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.16
  2. Affected versionversion=c52918744ee1e49cea86622a2633b9782446428f <4c4d866a64f36718cbcdf20add372a599dd44311
  3. Affected versionversion=c52918744ee1e49cea86622a2633b9782446428f <6f884eb87a79e0c482baef2ad96c96b81d024235
  4. Affected versionversion=c52918744ee1e49cea86622a2633b9782446428f <76fc5604308a109bf5838c2a0a0eb3ac6819f1ea

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.16; version=c52918744ee1e49cea86622a2633b9782446428f <4c4d866a64f36718cbcdf20add372a599dd44311; version=c52918744ee1e49cea86622a2633b9782446428f <6f884eb87a79e0c482baef2ad96c96b81d024235; version=c52918744ee1e49cea86622a2633b9782446428f <76fc5604308a109bf5838c2a0a0eb3ac6819f1ea

Published CVSS scores

2.5Amazon LinuxCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
7.8Linux kernel CVE teamCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.8CanonicalCVSS: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.

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

No observations available

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

Weakness, pattern, technique

No sourced classifications are available.

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

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo