Look up another CVE · open CVE-2026-74419 in the interactive tracker
CVE-2026-74419
accel/amdxdna: Adjust size for copy_to_user()
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem drivers/accel. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-74419 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The amount of data returned to user space should be limited by the buffer size provided by the application. If the buffer is smaller than the data size, return only the portion that fits instead of failing.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/accel/amdxdna/aie2_error.c
drivers/accel/amdxdna/aie2_message.c
drivers/accel/amdxdna/aie2_pci.c
- What this is
- AMD XDNA DRIVERMAINTAINERS section matched on drivers/accel/amdxdna/ · dri-devel@lists.freedesktop.org · Supported
- Kernel module
- amdxdna
Check it on the machine
grep -wE 'CONFIG_DRM_ACCEL|CONFIG_DRM_ACCEL_AMDXDNA' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w amdxdnaPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- ?
- not established - no Makefile entry for the affected file
- M
- a module where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_DRM_ACCEL, CONFIG_DRM_ACCEL_AMDXDNA
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-15 (2 months ago)source
- CVSS
- 7.3 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Lsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.16%, higher than 5.0% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/accel
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.14 | 7.1.5 | 097e57195ef8 |
| 6.14 | 7.2 | 6e87001fe19f |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The bug is reachable only through local DRM ioctls (DRM_IOCTL_AMDXDNA_GET_INFO and DRM_IOCTL_AMDXDNA_GET_ARRAY) on the /dev/accel/accel* character device after opening the AMD XDNA NPU driver; there is no network, adjacent-radio, or physical-bus attack path.
- AC:LAttack complexity, low
- On systems with the amdxdna driver loaded, an attacker reliably triggers the overflow by issuing a query ioctl with a valid userspace pointer and a buffer_size smaller than the fixed structure or response length; no races or victim-specific state are required.
- PR:LPrivileges required, low
- The vulnerable ioctls are registered without DRM_ROOT_ONLY (only SET_STATE requires root), so any unprivileged local user who can open the accel device node—typically members of the render/video group on Ryzen AI laptops—can invoke them without real root or init-namespace capabilities.
- UI:NUser interaction, none
- Exploitation requires only the attacker opening the accel device and calling the affected ioctls; no victim interaction such as mounting a filesystem or opening a file is needed.
- S:UScope, unchanged
- The flaw causes the kernel to write past the caller-supplied userspace buffer boundary, corrupting adjacent mappings in the attacking process; it does not cross VM, IOMMU, or other security boundaries into another authority.
- C:HConfidentiality impact, high
- Multiple handlers ignore args->buffer_size and copy full structure/response sizes via copy_to_user(), producing a controllable userspace heap overflow that can be developed into arbitrary memory read primitives, not merely bounded metadata disclosure.
- I:HIntegrity impact, high
- Ignoring buffer_size in copy_to_user() (e.g., aie2_get_aie_metadata, aie2_get_sensors, aie2_get_array_async_error, aie2_query_status/telemetry) allows out-of-bounds writes of up to hundreds of bytes to adjacent userspace memory, enabling heap corruption and potential code execution.
- A:LAvailability impact, low
- Repeated ioctl calls can corrupt or crash processes using the NPU (segfaults and workload failures), causing localized denial of service for ML/compute applications on affected Ryzen AI systems without necessarily panicking the kernel.