Review reviewCritical

CVE-2026-53046

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine ksmbd_crypt_message() sets a NULL completion callback on AEAD requests and does not handle the -EINPROGRESS return code from async hardware crypto engines like the Qualcomm Crypto Engine (QCE). When QCE returns -EINPROGRESS, ksmbd treats it as an error and immediately frees the request while the hardware DMA operation is still in flight. The DMA completion callback then dereferences freed memory, causing a NULL pointer crash: pc : qce_skcipher_done+0x24/0...

CVSS
9.8
EPSS
0.52%
41.4% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.52%
Technical severityCVSS 9.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free from async crypto on Qualcomm crypto engine ksmbd_crypt_message() sets a NULL completion callback on AEAD requests and does not handle the -EINPROGRESS return code from async hardware crypto engines like the Qualcomm Crypto Engine (QCE). When QCE returns -EINPROGRESS, ksmbd treats it as an error and immediately frees the request while the hardware DMA operation is still in flight. The DMA completion callback then dereferences freed memory, causing a NULL pointer crash: pc : qce_skcipher_done+0x24/0...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 < 57b47231055b431ed0a1a55f33cac32981564405, >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 < cc2da381875d4a67026e4c8feb3dba51a2a2d1bc, >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 < 8fcefe840fa8c14ce667768e5b043286ac3bbcbe, >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 < 8ef183216feaa24b66b940510d8b68f680eb56e9, >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 < 7164b3953cefd540e7ebca828c793bc6869cfbc4, >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 < b46aa129fa2807bfe1545fe74d9295d53c51520b, >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 < 3e298897f41c61450c2e7a4f457e8b2485eb35b3, >= 5.15, >= 5.15 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416