Kernel heap disclosure and corruption via SES descriptors
Published Oct 7, 2025 · Updated Oct 7, 2025
Out-of-bounds access in the Linux SCSI enclosure-services driver allows attackers to disclose or corrupt kernel memory. ses_enclosure_data_process() reads a device-supplied descriptor length before ensuring four header bytes remain, then writes a terminator without ensuring the descriptor body fits the diagnostic-page buffer. A malicious SCSI enclosure that supplies the page can expose adjacent heap bytes through sysfs, corrupt heap memory, or crash the host.
Summary
What happened
Out-of-bounds access in the Linux SCSI enclosure-services driver allows attackers to disclose or corrupt kernel memory. ses_enclosure_data_process() reads a device-supplied descriptor length before ensuring four header bytes remain, then writes a terminator without ensuring the descriptor body fits the diagnostic-page buffer. A malicious SCSI enclosure that supplies the page can expose adjacent heap bytes through sysfs, corrupt heap memory, or crash the host.
The record
- CVE
- CVE-2023-53675
- Published
- Oct 7, 2025
- Updated
- Oct 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, T1200
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 7, 2025CVE publishedPublication date reported by the CVE source.
- Oct 7, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <414418abc19fa4ccf730d273061a426c07a061d6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4b8cae410472653a59e15af62c57c49b8e0a1201
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <584892fd29a41ef424a148118a3103b16b94fb8c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <72021ae61a2bc6ca73cd593e255a10ed5f5dc5e7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <79ec5dd5fb07ecaea2f978c2d7a9f2f3526e4d19
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <801ab13d50cf3d26170ee073ea8bb4eececb76ab
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c315560e3ef77c1d822249f1743e647dc9c9912a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cffe09ca0555e235a42d6fa065e463c4b3d5b657
What conditions does exploitation require?
What is affected?
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.
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