# GSD-2023-1001497: rapidio: rio: fix possible name leak in rio_register_mport()

> A potential name leak in the RapidIO subsystem of the Linux kernel could allow local attackers to read sensitive kernel memory.

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

## What is GSD-2023-1001497?

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

### Official description

rapidio: rio: fix possible name leak in rio_register_mport()

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.10.163 by commit 97d9eb45ffa67ffa112a6659953321b8f7db0065, it was introduced in version v3.15 by commit 2aaf308b95b24649a6dcfed89cd956e972089b2a. For more details please see the references link.

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

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

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

## Is GSD-2023-1001497 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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