# GSD-2023-1000714: of: overlay: fix null pointer dereferencing in find_dup_cset_node_entry() and find_dup_cset_prop()

> A null pointer dereference in the Linux kernel's device tree overlay code can cause a system crash, requiring a kernel patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 17 Jan 2023

## What is GSD-2023-1000714?

GSD-2023-1000714 is a vulnerability in Kernel, published on 17 Jan 2023. 

### Official description

of: overlay: fix null pointer dereferencing in find_dup_cset_node_entry() and find_dup_cset_prop()

This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v6.0.16 by commit ab5bb7bbacf531de8e32912cc2e21f906113cee8, it was introduced in version v5.0 by commit 2fe0e8769df9fed5098daea7db933bc414c329d7. For more details please see the references link.

## Which versions are affected by GSD-2023-1000714?

1 open source package ship an affected version, including Kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Kernel` | Linux | All versions | None |

## How do I fix GSD-2023-1000714?

No fix has been published for GSD-2023-1000714 yet. Limit exposure of the affected software until one is available.

## Is GSD-2023-1000714 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2023-1000714 and fix it if it is affected.

What it is: GSD-2023-1000714 is a vulnerability in Kernel, published on 17 Jan 2023. 
Exploitation: There is no known exploitation of GSD-2023-1000714 in the wild and no public exploit code.

Affected packages and fixed versions:
- Kernel (Linux): affected all versions; no fix listed

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/GSD-2023-1000714/ (Markdown: https://insights.sbomify.com/GSD-2023-1000714/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2023-1000714

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