openSUSE-SU-2026:21019-1 Security update for rpcbind
Not scored
Published
Check this codebase for openSUSE-SU-2026:21019-1 and fix it if it is affected.
What it is: openSUSE-SU-2026:21019-1 is a memory corruption vulnerability in rpcbind, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2026:21019-1 in the wild and no public exploit code.
Affected product: rpcbind. 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/openSUSE-SU-2026-21019-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-21019-1/index.md)
An attacker can trigger a stack buffer overflow or unauthenticated oversized allocation in rpcbind, potentially leading to code execution or denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is openSUSE-SU-2026:21019-1?
openSUSE-SU-2026:21019-1 is a memory corruption vulnerability in rpcbind, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
This update for rpcbind fixes the following issues
- Update to rpcbind 1.2.9 (bsc#1267212) https://lore.kernel.org/linux-nfs/[email protected]/
- rpcinfo: stack buffer overflow in rpcinfo rpcbaddrlist()
- rpcbind: Stop unauthenticated oversized allocation in PMAPPROC_CALLIT decode
- rpcbind: fix memory leak in read_warmstart()
- rpcbind: fix memory leaks in network_init()
- rpcbind: fix memory leak in init_transport()
- Added -v (print version and compile flags)
- rpcinfo: Removed a number of "old-style function definition" warnings
- man/rpcbind: Update list of options
- Comment out ListenStream=@/run/rpcbind.sock
- [nfs/nfs-utils/rpcbind] rpcbind: avoid dereferencing NULL from realloc()
- systemd/rpcbind.service.in: Add various hardenings options
- man/rpcbind: Add Files section to manpage
- Moved rpcbind.lock and default configs to /run instead of /var/run
Which versions are affected by openSUSE-SU-2026:21019-1?
Linux distribution packages (1)
rpcbind openSUSE:Leap 16.0 | All versions | 1.2.9-160000.1.1 |
How do I fix openSUSE-SU-2026:21019-1?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is openSUSE-SU-2026:21019-1 being exploited?
There is no known exploitation of openSUSE-SU-2026:21019-1 in the wild and no public exploit code.