LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38606: crypto: qat - validate slices count returned by FW

In the Linux kernel, the following vulnerability has been resolved: crypto: qat - validate slices count returned by FW The function adf_send_admin_tl_start() enables the telemetry (TL) feature on a QAT device by sending the ICP_QAT_FW_TL_START message to the firmware. This triggers the FW to start writing TL data to a DMA buffer in memory and returns an array containing the number of accelerators of each type (slices) supported by this HW. The pointer to this array is stored in the adf_tl_hw_data data structure called slice_cnt. The array slice_cnt is then used in the function tl_print_dev_data() to report in debugfs only statistics about the supported accelerators. An incorrect value of the elements in slice_cnt might lead to an out of bounds memory read. At the moment, there isn't an implementation of FW that returns a wrong value, but for robustness validate the slice count array returned by FW.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects Intel QAT telemetry handling. The driver trusted slice-count data returned by firmware, which could cause an out-of-bounds memory read when debugfs reports QAT device statistics. The source says no known firmware currently returns the bad value, so urgency is controlled unless QAT is deployed broadly.

Executive priority

Treat as routine kernel maintenance unless the environment relies heavily on QAT acceleration. The current evidence does not indicate active exploitation or broad internet-facing risk, but patched kernels should be included in normal security update cycles.

Technical view

adf_send_admin_tl_start() stores firmware-returned QAT slice counts in slice_cnt. tl_print_dev_data() later uses those counts for debugfs telemetry output. Incorrect values could trigger an out-of-bounds memory read. The fix validates the firmware-provided slice count array before use.

Likely exposure

Exposure is likely limited to Linux systems using the QAT crypto driver and affected kernel builds. Systems without QAT hardware or without this driver path are less likely to be exposed. Exact distro impact requires checking vendor kernel backports.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. The Linux description explicitly says no current firmware implementation is known to return a wrong value. Evidence supports a robustness fix, not a known exploited issue.

Researcher notes

The bug is in QAT telemetry trust boundaries: firmware-provided slice counts feed debugfs reporting. Research should focus on affected kernel versions, vendor backports, QAT device presence, and whether local debugfs access is required to observe the faulty read path.

Mitigation direction

  • Apply Linux kernel vendor updates that include the linked stable fixes.
  • Prioritize systems with Intel QAT hardware or loaded QAT drivers.
  • Check distribution advisories for backported fixes and affected package versions.
  • Restrict unnecessary debugfs access according to existing hardening standards.

Validation and detection

  • Inventory Linux hosts for QAT hardware and loaded QAT kernel modules.
  • Map running kernel versions to vendor advisories and the linked stable commits.
  • Confirm patched kernels are deployed after maintenance windows.
  • Review whether debugfs is mounted and accessible on sensitive systems.
Prepared
Confidence
medium
Sources
5

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-38606 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
4Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux69e7649f7cc2aaa7889174456d39319a623c1a18, 69e7649f7cc2aaa7889174456d39319a623c1a18, 69e7649f7cc2aaa7889174456d39319a623c1a18unaffected
LinuxLinux6.8, 0, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

No CWE listed

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