CVE-2023-53493
Last modified
CVE-2023-53493 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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). EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
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)
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.4, < 6.4.7 | — |
| Linux | Linux Kernel | 6.5 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-53493?
How severe is CVE-2023-53493?
How do I fix CVE-2023-53493?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53488In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53489In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5349A memory leak flaw was found in ruby-magick, an interface be…3.3
- CVE-2023-53490In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2023-53491In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53492In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53494In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53495In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53496In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53497In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53498In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53499In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53493?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
