# SUSE-SU-2026:3199-1: Security update for multipath-tools

> Attackers can trigger heap overflows or unbounded writes via crafted USB or DASD devices, potentially causing crashes or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Jul 2026

## What is SUSE-SU-2026:3199-1?

SUSE-SU-2026:3199-1 is a vulnerability in multipath-tools, published on 22 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

This update for multipath-tools fixes the following issues

- kpartx: integer overflow in the GPT partition table size calculation can lead to heap OOB read via crafted USB device
  or disk image(bsc#1268145).
- kpartx: missing bounds check can lead to a DASD VOL1 unbounded array write via a crafted DASD disk with more than 256
  consecutive format labels (bsc#1268144).

## Which versions are affected by SUSE-SU-2026:3199-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `multipath-tools` | SUSE:Linux Enterprise Micro 5.3 | All versions | 0.9.0+168+suse.54b6b26-150400.4.22.1 |
| `multipath-tools` | SUSE:Linux Enterprise Micro 5.4 | All versions | 0.9.0+168+suse.54b6b26-150400.4.22.1 |

## How do I fix SUSE-SU-2026:3199-1?

Apply the vendor's patch.

## Is SUSE-SU-2026:3199-1 being exploited?

There is no known exploitation of SUSE-SU-2026:3199-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2026:3199-1 and fix it if it is affected.

What it is: SUSE-SU-2026:3199-1 is a vulnerability in multipath-tools, published on 22 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of SUSE-SU-2026:3199-1 in the wild and no public exploit code.

Affected product: multipath-tools. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/SUSE-SU-2026-3199-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-3199-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2026:3199-1

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