Kernel memory corruption via unchecked DMA mapping failure
Published May 17, 2024 · Updated Aug 5, 2026
Unchecked return handling in the Linux kernel safexcel driver allows remote attackers to corrupt kernel memory or crash affected appliances. In safexcel_cipher.c, the request path continues after dma_map_sg() returns zero, so the engine can consume stale or unmapped scatter-gather DMA addresses; the patch adds failure checks and unwinds earlier mappings. Exposure requires an EIP97/EIP197 safexcel engine and a reachable IPsec security association; crafted ESP traffic can trigger memory corruption, disclosure, or a kernel panic without target credentials.
Summary
What happened
Unchecked return handling in the Linux kernel safexcel driver allows remote attackers to corrupt kernel memory or crash affected appliances. In safexcel_cipher.c, the request path continues after dma_map_sg() returns zero, so the engine can consume stale or unmapped scatter-gather DMA addresses; the patch adds failure checks and unwinds earlier mappings. Exposure requires an EIP97/EIP197 safexcel engine and a reachable IPsec security association; crafted ESP traffic can trigger memory corruption, disclosure, or a kernel panic without target credentials.
The record
- CVE
- CVE-2023-52687
- Published
- May 17, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-252, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=49186a7d9e46ff132a0ed9b721ad6b6a58dba6c1 <4c0ac81a172a69a7733290915276672787e904ec
- Affected versionversion=49186a7d9e46ff132a0ed9b721ad6b6a58dba6c1 <8084b788c2fb1260f7d44c032d5124680b20d2b2
- Affected versionversion=49186a7d9e46ff132a0ed9b721ad6b6a58dba6c1 <87e02063d07708cac5bfe9fd3a6a242898758ac8
- Affected versionversion=49186a7d9e46ff132a0ed9b721ad6b6a58dba6c1 <fc0b785802b856566df3ac943e38a072557001c4
- Affected versionversion=6.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo