# CVE-2023-53803: scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()

> A slab-out-of-bounds read in the Linux kernel SES driver can cause a system crash, requiring a kernel patch to prevent denial of service.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2023-53803, DEBIAN-CVE-2023-53803, GHSA-7mw7-q5qp-mcqq, UBUNTU-CVE-2023-53803

## What is CVE-2023-53803?

CVE-2023-53803 is a high-severity memory corruption vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2023-53803?


## How do I fix CVE-2023-53803?

Apply the vendor's patch.

## Is CVE-2023-53803 being exploited?

There is no known exploitation of CVE-2023-53803 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-53803 and fix it if it is affected.

What it is: CVE-2023-53803 is a high-severity memory corruption vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-53803 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-53803/ (Markdown: https://insights.sbomify.com/CVE-2023-53803/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-53803
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-53803
- OSV: https://osv.dev/vulnerability/CVE-2023-53803

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-53803/
Summaries are generated and may contain mistakes; the official description above is the record.