# CVE-2023-4881: CVE-2023-4881 was wrongly assigned to a bug that was deemed to be a non-security issue by the Linux kernel security team.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Sep 2023
- **Updated:** 20 Sep 2023
- **Also known as:** BELL-CVE-2023-4881, GHSA-3mq5-2hmg-6cr7, UBUNTU-CVE-2023-4881, openSUSE-SU-2024:13245-1

## What is CVE-2023-4881?

CVE-2023-4881 is a vulnerability in kernel-source, published on 11 Sep 2023. 

### Official description

CVE-2023-4881 was wrongly assigned to a bug that was deemed to be a non-security issue by the Linux kernel security team.

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-source` | openSUSE:Tumbleweed | All versions | 6.5.4-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2023-4881 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4881 is a vulnerability in kernel-source, published on 11 Sep 2023. 
Exploitation: There is no known exploitation of CVE-2023-4881 in the wild and no public exploit code.

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

## Sources

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

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