CVE-2023-4610 The SRCU code was added in upstream kernel v6.4-rc1 and removed before v6.4.
Not scored
Updated
Check this codebase for CVE-2023-4610 and fix it if it is affected.
What it is: CVE-2023-4610 is a vulnerability.
Exploitation: There is no known exploitation of CVE-2023-4610 in the wild and no public exploit code.
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-4610/ (Markdown: https://insights.sbomify.com/CVE-2023-4610/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2023-4610?
CVE-2023-4610 is a vulnerability.
Official description
The SRCU code was added in upstream kernel v6.4-rc1 and removed before v6.4. This bug only existed in development kernels. Please see https://lore.kernel.org/all/[email protected] and https://bugzilla.suse.com/show_bug.cgi?id=1215932 for more information.
Which versions are affected by CVE-2023-4610?
How do I fix CVE-2023-4610?
No fix has been published for CVE-2023-4610 yet. Limit exposure of the affected software until one is available.
Is CVE-2023-4610 being exploited?
There is no known exploitation of CVE-2023-4610 in the wild and no public exploit code.
Sources
Also known as UBUNTU-CVE-2023-4610.