LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53493: accel/qaic: tighten bounds checking in decode_message()

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)

HighCVSS 8.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux’s accel/qaic driver could allow malformed messages to corrupt kernel memory. Successful abuse could compromise data, alter system behavior, or crash the host. The supplied CVSS score is 8.4, but the attack vector is local, so ordinary internet exposure alone does not establish vulnerability.

Executive priority

Treat as high priority on systems using accel/qaic, especially shared or sensitive compute hosts. Prioritize exposure discovery and vendor-supported patching. Lower urgency is reasonable only after confirming the driver is absent, unused, or the stable correction is already backported.

Technical view

decode_message() insufficiently validated message and transport-header lengths. This could produce negative or overflowing size calculations and unsafe memory copying in decode_passthrough(). The stable patches add minimum-header checks, remaining-buffer validation, and overflow-safe size_add() arithmetic.

Likely exposure

Exposure is limited to systems with an affected Linux kernel and relevant accel/qaic functionality. The supplied version metadata identifies 6.4-era and 6.5 entries but is insufficiently clear for precise range conclusions. Confirm each distribution kernel against vendor guidance and the cited stable fixes.

Exploitation context

The supplied record does not establish active exploitation, and KEV is false. No public exploit is identified in the bundle. CVSS characterizes exploitation as local, low complexity, requiring no privileges or user interaction, with potentially high confidentiality, integrity, and availability impact.

Researcher notes

The correction validates space for headers, rejects undersized transport headers, checks message advancement against remaining capacity, and prevents addition overflow. These controls protect a memcpy length calculation in decode_passthrough(). The sources do not specify a CWE or fully document how attacker-controlled data reaches this decoder, leaving practical exploitation prerequisites uncertain.

Mitigation direction

  • Install a vendor kernel update containing the cited stable decode_message() fix.
  • Prioritize systems where the accel/qaic driver is loaded or QAIC functionality is used.
  • If patching is delayed, consult vendor guidance about safely disabling unused accel/qaic functionality.
  • Follow distribution advisories because downstream kernel versions may not match upstream numbering.

Validation and detection

  • Inventory deployed kernel versions and identify systems using the accel/qaic driver.
  • Verify whether each deployed kernel includes either cited stable fix or an equivalent backport.
  • Confirm the running kernel changed after remediation, not merely the installed package.
  • Review vendor advisories to resolve the ambiguous affected-version metadata.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53493 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2023-53493Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux129776ac2e38231fa9c02ce20e116c99de291666, 129776ac2e38231fa9c02ce20e116c99de291666unaffected
LinuxLinux6.4, 0, 6.4.7, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.