CVE-2023-53521

What it actually does

Out-of-bounds memory read in the SES SCSI enclosure services driver during module removal when the number of components is zero, triggering KASAN slab-out-of-bounds in ses_intf_remove().

Why it matters to the business

May cause kernel crashes or memory disclosure on affected Linux systems during hardware management operations, potentially leading to system instability in storage environments with high downstream kernel dependents.

How an attack unfolds

An attacker with local privileges triggers ses module removal under conditions where edev->components is zero, resulting in invalid access to the component array; unrelated mentions of VMSCAPE or container privilege escalation campaigns do not apply to this kernel memory issue.

How to fix it

Update the Linux kernel to a version containing commit 76f7050537476ac062ec23a544fbca8270f2d08b; no CISA KEV deadline applies.

How to confirm the fix worked

Confirm the ses_intf_remove() function no longer accesses component[0] when components is zero; verify kernel build includes the referenced commit and test rmmod under zero-component conditions.

Typical attack path

1. Obtain local user access on a Linux system
2. Ensure or force conditions where SES device reports zero components
3. Unload the ses kernel module to trigger the faulty removal path

How to detect it

Search kernel logs and dmesg for KASAN reports mentioning slab-out-of-bounds in ses_intf_remove; check for rmmod processes coinciding with SES device events.

• BUG: KASAN: slab-out-of-bounds in ses_intf_remove+0x23f/0x270 [ses]
• Read of size 8 at addr ffff88a10d32e5d8 by task rmmod

What your security team should do

• Apply the fixed kernel commit across all affected distributions
• Prioritize patching in storage and server fleets due to 394 days since publication
• Monitor EPSS trend and kernel oops logs for related crashes