Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2023-52687

In the Linux kernel's safexcel crypto driver, the dma_map_sg() macro can return zero to indicate an error, but the code did not check for this condition. This flaw could allow improper handling of DMA mappings, potentially leading to memory corruption or other security impacts. A patch has been added that checks the return value and ensures previously mapped buffers are properly unmapped.

publishedMay 17, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
45th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 4, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel users employing the safexcel crypto driver.

02

Real-world impact

An attacker could exploit this flaw to cause denial of service, information disclosure, or possibly execute arbitrary code with kernel privileges.

03

Why this severity

CVSS v3.1 base score 9.8 (Critical) due to network‑adjacent attack vector, low complexity, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 011. Obtain the Linux kernel patch that adds error handling for dma_map_sg() calls in the safexcel crypto driver (addresses CVE-2023-52687).
  2. 022. Apply the patch to the affected kernel source tree.
  3. 033. Recompile the kernel with the patch applied.
  4. 044. Install the updated kernel and reboot the system.

NVD description states the vulnerability has been resolved by adding error handling for dma_map_sg() calls.

05

Timeline

  1. May 17, 2024 · May 17, 2024
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 5, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →