LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26974: crypto: qat - resolve race condition during AER recovery

In the Linux kernel, the following vulnerability has been resolved: crypto: qat - resolve race condition during AER recovery During the PCI AER system's error recovery process, the kernel driver may encounter a race condition with freeing the reset_data structure's memory. If the device restart will take more than 10 seconds the function scheduling that restart will exit due to a timeout, and the reset_data structure will be freed. However, this data structure is used for completion notification after the restart is completed, which leads to a UAF bug. This results in a KFENCE bug notice. BUG: KFENCE: use-after-free read in adf_device_reset_worker+0x38/0xa0 [intel_qat] Use-after-free read at 0x00000000bc56fddf (in kfence-#142): adf_device_reset_worker+0x38/0xa0 [intel_qat] process_one_work+0x173/0x340 To resolve this race condition, the memory associated to the container of the work_struct is freed on the worker if the timeout expired, otherwise on the function that schedules the worker. The timeout detection can be done by checking if the caller is still waiting for completion or not by using completion_done() function.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A timing flaw in the Linux Intel QAT driver can access memory after it has been freed when PCI error recovery takes longer than ten seconds. This can crash or corrupt an affected system. The supplied CVSS assessment is 7.8, but exposure is limited to systems using the affected driver and recovery path.

Executive priority

Treat this as a high-priority, hardware-specific kernel update rather than an internet-wide emergency. Promptly identify QAT-enabled systems, then patch through supported vendor channels. Accelerate remediation where untrusted local users or workloads exist. No active exploitation is established by the supplied sources.

Technical view

During PCI AER recovery, the restart scheduler may time out and free reset_data while adf_device_reset_worker later uses it for completion notification, causing a use-after-free read. The kernel fix assigns cleanup to the worker after a timeout, or to the scheduling function when completion occurs before timeout, using completion_done() to distinguish the paths.

Likely exposure

Likely exposure is concentrated on listed affected Linux versions where the Intel QAT driver and relevant hardware are present. Triggering requires the PCI AER recovery path and a device restart exceeding ten seconds. Systems without Intel QAT use are unlikely to reach the vulnerable code. The bundle does not establish how commonly these conditions occur.

Exploitation context

The CVSS vector describes local access, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact. However, the supplied evidence demonstrates a KFENCE use-after-free notice, not successful exploitation. The CVE is not listed as KEV, and no cited source in the bundle confirms active exploitation.

Researcher notes

The critical condition is lifetime ownership of reset_data across asynchronous recovery and timeout paths. The reported manifestation is a KFENCE read in adf_device_reset_worker. Researchers should verify branch-specific backports and vendor package status. The source bundle provides neither a demonstrated privilege-escalation outcome nor evidence that confidentiality or integrity impact has been reproduced.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the applicable stable Linux fix.
  • Review Linux distribution and appliance vendor advisories for corrected package versions.
  • Prioritize systems that load the Intel QAT driver or use Intel QAT hardware.
  • Restrict unnecessary local access until affected systems are updated.
  • Test kernel updates against hardware acceleration workloads before production rollout.

Validation and detection

  • Inventory kernel releases across Linux hosts and compare them with vendor advisories.
  • Identify systems using Intel QAT hardware or loading the Intel QAT driver.
  • Confirm the installed kernel changelog includes the applicable referenced stable fix.
  • Review kernel logs for PCI AER recovery, QAT reset timeouts, or use-after-free notices.
  • After updating, exercise approved recovery testing and confirm normal QAT operation.
Prepared
Confidence
high
Sources
6

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.

description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-26974 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
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
3ADP providers
13Source links

SSVC decision data

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

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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-26974Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd8cba25d2c68992a6e7c1d329b690a9ebe01167d, d8cba25d2c68992a6e7c1d329b690a9ebe01167d, d8cba25d2c68992a6e7c1d329b690a9ebe01167d, d8cba25d2c68992a6e7c1d329b690a9ebe01167d, d8cba25d2c68992a6e7c1d329b690a9ebe01167d, d8cba25d2c68992a6e7c1d329b690a9ebe01167d, d8cba25d2c68992a6e7c1d329b690a9ebe01167d, d8cba25d2c68992a6e7c1d329b690a9ebe01167d, d8cba25d2c68992a6e7c1d329b690a9ebe01167dunaffected
LinuxLinux3.17, 0, 4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.84, 6.6.24, 6.7.12, 6.8.3, 6.9affected
Weakness

CWE details

No CWE listed

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