CVE-2026-64529

crypto: qat - remove unused character device and IOCTLs

HIGH
7.8
CVSS Score
Published: July 25, 2026 at 09:24 AM UTC
Updated: October 24, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: qat - remove unused character device and IOCTLs The QAT driver exposes a character device (qat_adf_ctl) with IOCTLs for device configuration, start, stop, status query and enumeration. These IOCTLs are not part of any public uAPI header and have no known in-tree or out-of-tree users. Device lifecycle is already managed via sysfs. The ioctl interface also increases the attack surface and is the subject of a number of bug reports. Remove the character device, the IOCTL definitions, and the related data structures (adf_dev_status_info, adf_user_cfg_key_val, adf_user_cfg_section, adf_user_cfg_ctl_data). Drop the now-unused adf_cfg_user.h header and strip adf_ctl_drv.c down to the minimal module_init/module_exit hooks for workqueue, AER, and crypto/compression algorithm registration. Clean up leftover dead code that was only reachable from the removed IOCTL paths: adf_cfg_del_all(), adf_devmgr_verify_id(), adf_devmgr_get_num_dev(), adf_devmgr_get_dev_by_id(), adf_get_vf_real_id() and the unused ADF_CFG macros. Additionally, drop the entry associated to QAT IOCTLs in ioctl-number.rst.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.17d8cba25d2c68992a6e7c1d329b690a9ebe01167d
Vendor states this is fixed in 071590a44cbc38483fceb1ab943363ec26868e1b (fixed)
Vendor states this is fixed in 1de076f43e64bf65fbe7280a269c70e0e60518df (fixed)
Vendor states this is fixed in 3ae49dd04dbb11fb73f17f58a982dba128abe83a (fixed)
Vendor states this is fixed in 6848a6e39cac44fdb7cb88f0f777df62172d1551 (fixed)
Vendor states this is fixed in a4999664a5ef77bdb0c6e6b935f581ac8ce6b63a (fixed)
Vendor states this is fixed in b1ea97076bd0a5196290deba172034e480646727 (fixed)
Vendor states this is fixed in b8ebf008696de1ec08c90d51f94d7e40bd448be1 (fixed)
Vendor states this is fixed in d237230728c567297f2f98b425d63156ab2ed17f (fixed)
Vendor states this is fixed in de2cc38489b629927910b1aeff69bba7bd5c6f1b (fixed)
Vendor states this is fixed in 3.17 (unaffected)
Vendor states this is fixed in 5.10.260 (unaffected)
Vendor states this is fixed in 5.15.211 (unaffected)
Vendor states this is fixed in 6.1.177 (unaffected)
Vendor states this is fixed in 6.12.95 (unaffected)
Vendor states this is fixed in 6.18.37 (unaffected)
Vendor states this is fixed in 6.6.144 (unaffected)
Vendor states this is fixed in 7.0.14 (unaffected)
Vendor states this is fixed in 7.1.2 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-489

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card