# OSV-2026-795: Stack-buffer-underflow in probe_dasd_pt

> A stack-buffer-underflow in the Linux kernel DASD probe function can cause a crash, requiring local access to exploit.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2026

## What is OSV-2026-795?

OSV-2026-795 is a memory corruption vulnerability in util-linux, published on 22 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=514896889

```
Crash type: Stack-buffer-underflow READ 1
Crash state:
probe_dasd_pt
idinfo_probe
partitions_probe
```

## Which versions are affected by OSV-2026-795?

1 open source package ship an affected version, including util-linux.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `util-linux` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2026-795?

No fix has been published for OSV-2026-795 yet. Limit exposure of the affected software until one is available.

## Is OSV-2026-795 being exploited?

There is no known exploitation of OSV-2026-795 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2026-795 and fix it if it is affected.

What it is: OSV-2026-795 is a memory corruption vulnerability in util-linux, published on 22 May 2026. 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 OSV-2026-795 in the wild and no public exploit code.

Affected packages and fixed versions:
- util-linux (OSS-Fuzz): 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/OSV-2026-795/ (Markdown: https://insights.sbomify.com/OSV-2026-795/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2026-795

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