CVE-2023-53803
Description
In the Linux kernel, the following vulnerability has been resolved:
scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()
A fix for:
BUG: KASAN: slab-out-of-bounds in ses_enclosure_data_process+0x949/0xe30 [ses] Read of size 1 at addr ffff88a1b043a451 by task systemd-udevd/3271
Checking after (and before in next loop) addl_desc_ptr[1] is sufficient, we expect the size to be sanitized before first access to addl_desc_ptr[1]. Make sure we don't walk beyond end of page.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A slab-out-of-bounds read in the Linux kernel's SES driver occurs when processing enclosure data, due to insufficient bounds checking before accessing addl_desc_ptr[1].
What the vulnerability is
In the Linux kernel's SCSI Enclosure Services (SES) driver, the function ses_enclosure_data_process() contains a slab-out-of-bounds read flaw. The KASAN report indicates a read of size 1 at an out-of-bounds address addr ffff88a1b043a451. The root cause is that the code does not properly verify that the additional descriptor pointer (addl_desc_ptr[1]) is within the allocated page boundary before accessing it. The fix ensures that the size is sanitized before the first access to addl_desc_ptr[1] and that the loop does not walk beyond the end of the page [1][2][3].
How it is exploited
An attacker with physical access or the ability to provide a maliciously crafted SES page (e.g., via a specially crafted SCSI enclosure) could trigger this bug. The vulnerability is reachable during normal system operation when udev processes enclosure events. No special privileges beyond the ability to supply the SES data are required, but the attacker must control the enclosure device to supply malformed descriptor data that causes the driver to read beyond the allocated buffer [1][2][3].
Impact
A successful exploit can cause a kernel crash (denial of service) due to an out-of-bounds memory read. In some cases, the out-of-bounds access might be leveraged further to leak sensitive kernel memory or potentially achieve code execution, though the provided references focus on the crash potential [1][2][3].
Mitigation status
The fix has been incorporated into the Linux kernel stable tree as commits visible in references [1], [2], and [3]. Systems should apply the latest kernel updates or backport the patch to prevent exploitation. No workaround is mentioned by the vendor [1][2][3].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
8da1a955c48a19e5c7d52085b467afb1dd630e4dd25da784b2b28a7d261cb0dfe68394cbe799e8dd2022d9b4f5028e493Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/0dfe68394cbe1d4fe579fb325ecc813c50528c5anvd
- git.kernel.org/stable/c/2b28a7d261cb309912596d6a2d383ca370483527nvd
- git.kernel.org/stable/c/467afb1dd630d8c6d172bd6cacc125199b5f4f2dnvd
- git.kernel.org/stable/c/799e8dd2022d2e13f0c5c1906b40ceca07a23349nvd
- git.kernel.org/stable/c/9b4f5028e493cb353a5c8f5c45073eeea0303abdnvd
- git.kernel.org/stable/c/9e5c7d52085b8c84bc82a261580f0eb170039325nvd
- git.kernel.org/stable/c/da1a955c48a16e16e925d6544793914e52a6fa51nvd
- git.kernel.org/stable/c/e4dd25da784b2e07dbfbf04509afa4c5a1375227nvd
News mentions
0No linked articles in our index yet.