# SUSE-SU-2026:1422-1: Security update for smc-tools


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 17 Apr 2026

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

SUSE-SU-2026:1422-1 is a vulnerability in smc-tools, published on 17 Apr 2026. 

### Official description

This update for smc-tools fixes the following issue:

Update to smc-tools v1.8.7:

- predictable /tmp file allows for local denial of service (bsc#1230052).

Changelog:

Update to v1.8.7:
  
 - smc_rnics: fix regression when PFT not available
 - smcd/smcr: prevent DoS on statistics workfile present in /tmp/
  
Update to v1.8.6:

 - man pages: Update man page for smc_pnet
 - smc-tools: Display sndbuf/RMB stats only if supported by the kernel
  
Update to v1.8.5:
 
 - smc_rnics: Add support for Network Express RNIC in smc_rnics
 - smc_rnics: Add PFT and VF columns to smc_rnics output
 - libnetlink..: Fix function declaration to use a void prototype
 - smc_rnics: Update smc_chk to extract PNetID from column 9
 - man pages: Update man page for --rawids option and PFT and VF columns
 - smc_rnics: Fix missing PPrt values in smc_rnics -r output

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `smc-tools` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 1.8.7-150600.3.6.1 |
| `smc-tools` | openSUSE:Leap 15.6 | All versions | 1.8.7-150600.3.6.1 |

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2026:1422-1 is a vulnerability in smc-tools, published on 17 Apr 2026. 
Exploitation: There is no known exploitation of SUSE-SU-2026:1422-1 in the wild and no public exploit code.

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

## Sources

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

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