# GSD-2022-1008223: ftrace: Fix null pointer dereference in ftrace_add_mod()

> A null pointer dereference in the Linux kernel ftrace module can cause a system crash, requiring local privileged access to exploit.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2022

## What is GSD-2022-1008223?

GSD-2022-1008223 is a vulnerability in Kernel, published on 8 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ftrace: Fix null pointer dereference in ftrace_add_mod()

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 v4.19.267 by commit b5bfc61f541d3f092b13dedcfe000d86eb8e133c, it was introduced in version v4.13 by commit 673feb9d76ab3eddde7acfd94b206e321cfc90b9. For more details please see the references link.

## Which versions are affected by GSD-2022-1008223?

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-2022-1008223?

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

## Is GSD-2022-1008223 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2022-1008223 and fix it if it is affected.

What it is: GSD-2022-1008223 is a vulnerability in Kernel, published on 8 Dec 2022. 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 GSD-2022-1008223 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-2022-1008223/ (Markdown: https://insights.sbomify.com/GSD-2022-1008223/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2022-1008223

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