# GSD-2023-1000276: af_unix: Get user_ns from in_skb in unix_diag_get_exact().

> A local attacker can potentially read sensitive kernel memory via the unix_diag_get_exact function due to incorrect user namespace handling.

- **Severity:** Not scored
- **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:** No
- **Published:** 17 Jan 2023

## What is GSD-2023-1000276?

GSD-2023-1000276 is a vulnerability in Kernel, published on 17 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

af_unix: Get user_ns from in_skb in unix_diag_get_exact().

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 v5.4.227 by commit c66d78aee55dab72c92020ebfbebc464d4f5dd2a, it was introduced in version v5.3 by commit cae9910e73446cac68a54e3a7b02aaa12b689026. For more details please see the references link.

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

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-1000276?

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

## Is GSD-2023-1000276 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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