# CVE-2023-1078: Memory corruption in Linux kernel

> A type confusion flaw in the Linux kernel RDS protocol allows local attackers to cause out-of-bounds access and lock corruption, potentially leading to privilege escalation or denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2023
- **Updated:** 5 May 2025
- **Also known as:** DEBIAN-CVE-2023-1078, GHSA-r26p-gh73-qgq9, SUSE-SU-2023:1610-1, SUSE-SU-2023:1645-1, UBUNTU-CVE-2023-1078, openSUSE-SU-2024:12814-1

## What is CVE-2023-1078?

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

### Official description

A flaw was found in the Linux Kernel in RDS (Reliable Datagram Sockets) protocol. The rds_rm_zerocopy_callback() uses list_entry() on the head of a list causing a type confusion. Local user can trigger this with rds_message_put(). Type confusion leads to `struct rds_msg_zcopy_info *info` actually points to something else that is potentially controlled by local user. It is known how to trigger this, which causes an out of bounds access, and a lock corruption.

Weakness: CWE-843 (Access of Resource Using Incompatible Type), CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-livepatch-SLE15-SP2_Update_34` | SUSE:Linux Enterprise Live Patching 15 SP2 | All versions | 2-150200.2.3 |
| `kernel-livepatch-SLE15-SP3_Update_30` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 2-150300.2.3 |
| `kernel-source` | openSUSE:Tumbleweed | All versions | 6.2.8-1.1 |

Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2023-1078 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-1078 is a high-severity memory corruption vulnerability in Linux kernel, published on 27 Mar 2023. 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-1078 in the wild and no public exploit code.

Affected product: Linux kernel. 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-1078/ (Markdown: https://insights.sbomify.com/CVE-2023-1078/index.md)
```

## Sources

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

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