Host crash via invalid enclosure teardown free
Published Sep 18, 2025 · Updated Sep 18, 2025
Denial of service in the Linux kernel SCSI enclosure-services driver allows attackers to crash the host via a zero-component enclosure. When ses_intf_add records zero components, ses_intf_remove_enclosure dereferences edev->component[0].scratch and passes an invalid pointer to kfree during teardown. A reachable SES target must advertise no device components and then disconnect; the resulting invalid free causes a kernel oops or panic.
Summary
What happened
Denial of service in the Linux kernel SCSI enclosure-services driver allows attackers to crash the host via a zero-component enclosure. When ses_intf_add records zero components, ses_intf_remove_enclosure dereferences edev->component[0].scratch and passes an invalid pointer to kfree during teardown. A reachable SES target must advertise no device components and then disconnect; the resulting invalid free causes a kernel oops or panic.
The record
- CVE
- CVE-2023-53431
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 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 <3fe97ff3d94934649abb0652028dd7296170c8d0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4863fefc8a8cc8e8f6c7635b12d9dffaa0a12d86
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ca5470b33e5221dd3e5be81108697c22dd38b56
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6069e04a922a0488bcf4f1017d38d18afda8194c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6fce2307650a190e343a84537c278d499fa37c26
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d68937dfc73ee7f61cf3424fa3225be93cacaa00
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f182ad02024d3f45374a9e0c9d76f28b776d762d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <feefd5232ecb788f0666f75893a7a86faec8bbcc
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