LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26753: crypto: virtio/akcipher - Fix stack overflow on memcpy

In the Linux kernel, the following vulnerability has been resolved: crypto: virtio/akcipher - Fix stack overflow on memcpy sizeof(struct virtio_crypto_akcipher_session_para) is less than sizeof(struct virtio_crypto_op_ctrl_req::u), copying more bytes from stack variable leads stack overflow. Clang reports this issue by commands: make -j CC=clang-14 mrproper >/dev/null 2>&1 make -j O=/tmp/crypto-build CC=clang-14 allmodconfig >/dev/null 2>&1 make -j O=/tmp/crypto-build W=1 CC=clang-14 drivers/crypto/virtio/ virtio_crypto_akcipher_algs.o

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26753 is a Linux kernel bug in the virtio crypto asymmetric cipher code. A memory copy can overwrite stack data because it copies a larger structure into a smaller stack variable. The public sources confirm kernel fixes, but do not provide a severity score, impact rating, or active exploitation evidence.

Executive priority

Track this through normal kernel patch governance unless asset inventory shows exposed virtio crypto use on affected kernels. Escalate if critical systems cannot receive vendor kernel updates promptly, because the issue is in kernel memory handling.

Technical view

The flaw is in drivers/crypto/virtio/akcipher. The vulnerable code copies sizeof(virtio_crypto_op_ctrl_req::u) into a virtio_crypto_akcipher_session_para stack object, whose size is smaller, causing stack overflow. The issue was identified by Clang build diagnostics and fixed in Linux stable commits.

Likely exposure

Exposure is likely limited to Linux kernels containing the affected virtio crypto akcipher code path. Systems using vendor kernels that include the listed stable fixes should not be considered exposed based on the provided sources. The bundle does not prove which distributions or configurations load this driver by default.

Exploitation context

The source bundle does not report public exploitation, weaponized proof of concept, or KEV listing. Exploitability and attacker prerequisites are not described. Treat this as a kernel memory-safety issue requiring patch tracking, especially in virtualized environments using virtio crypto functionality.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploitation status, or detailed impact is provided. The strongest facts are the kernel commit description, affected Linux version metadata, stable fix references, and Debian LTS advisory. Avoid assuming privilege escalation or remote reachability without more vendor analysis.

Mitigation direction

  • Apply vendor Linux kernel updates that include the referenced stable fixes.
  • For Debian LTS systems, review and apply the cited Debian security update.
  • Map running kernels to vendor advisories or the listed Linux stable commits.
  • If updates are unavailable, check vendor guidance before changing virtio crypto configuration.

Validation and detection

  • Inventory running Linux kernel versions across affected assets.
  • Confirm installed kernel changelogs reference CVE-2024-26753 or the stable commits.
  • Check whether virtio crypto support is built or loaded where relevant.
  • Verify patched kernels are active after reboot, not only installed.
Prepared
Confidence
medium
Sources
8

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-2024-26753 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1ff57428894fc4f5001d3df0762c1820295d6c4f, 59ca6c93387d325e96577d8bd4c23c78c1491c11, 59ca6c93387d325e96577d8bd4c23c78c1491c11, 59ca6c93387d325e96577d8bd4c23c78c1491c11, 59ca6c93387d325e96577d8bd4c23c78c1491c11, 5.10.209unaffected
LinuxLinux5.18, 0, 5.10.212, 6.1.80, 6.6.19, 6.7.7, 6.8affected
Weakness

CWE details

No CWE listed

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