CVE-2023-53493 json
accel/qaic: tighten bounds checking in decode_message()
published 2025-10-01 13 mo ago modified 2026-08-05 3 mo ago also EUVD-2025-32790
- cvss
- 8.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
accel/qaic: tighten bounds checking in decode_message()
Copy the bounds checking from encode_message() to decode_message().
This patch addresses the following concerns. Ensure that there is enough space for at least one header so that we don't have a negative size later.
if (msg_hdr_len < sizeof(*trans_hdr))
Ensure that we have enough space to read the next header from the msg->data.
if (msg_len > msg_hdr_len - sizeof(*trans_hdr)) return -EINVAL;
Check that the trans_hdr->len is not below the minimum size:
if (hdr_len < sizeof(*trans_hdr))
This minimum check ensures that we don't corrupt memory in decode_passthrough() when we do.
memcpy(out_trans->data, in_trans->data, len - sizeof(in_trans->hdr));
And finally, use size_add() to prevent an integer overflow:
if (size_add(msg_len, hdr_len) > msg_hdr_len)
Patch / fix
- Linux Linux 6.4.7, 6.5
- linux Debian 14, Debian 13 6.4.11-1
debian advisories DEBIAN-CVE-2023-53493
- kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.22.1
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.22.1
- kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.22.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.18.1
- kernel-syms-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.18.1
- kernel-source-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.18.1
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.22.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.22.1
suse advisories SUSE-SU-2025:4141-1SUSE-SU-2025:4132-1SUSE-SU-2025:4057-1SUSE-SU-2025:20870-1SUSE-SU-2025:20898-1SUSE-SU-2025:3751-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-53493 updated
kernel: accel/qaic: tighten bounds checking in decode_message()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
Sources
- CVE List CVE-2023-53493
- NVD CVE-2023-53493
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.