# ALBA-2021:2573: sanlock bug fix and enhancement update

> A bug in sanlock caused closed connections and released leases upon receiving bad client messages, potentially disrupting shared storage synchronization.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 29 Jun 2021

## What is ALBA-2021:2573?

ALBA-2021:2573 is a vulnerability in sanlock-devel, published on 29 Jun 2021. 

### Official description

The sanlock packages provide a shared storage lock manager. Hosts with
shared access to a block device or a file can use sanlock to synchronize
their activities. VDSM and libvirt use sanlock to synchronize access to
shared devices or files.

Bug Fix(es) and Enhancement(s):

* bad client message causes closed connection and released leases
(BZ#1965481)

* Expose sanlock_inquire() in python bindings (BZ#1965483)

## Which versions are affected by ALBA-2021:2573?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sanlock-devel` | AlmaLinux:8 | All versions | 3.8.3-3.el8_4 |

## How do I fix ALBA-2021:2573?

Apply the vendor's patch.

## Is ALBA-2021:2573 being exploited?

There is no known exploitation of ALBA-2021:2573 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2021:2573 and fix it if it is affected.

What it is: ALBA-2021:2573 is a vulnerability in sanlock-devel, published on 29 Jun 2021. 
Exploitation: There is no known exploitation of ALBA-2021:2573 in the wild and no public exploit code.

Affected product: sanlock-devel. 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/ALBA-2021-2573/ (Markdown: https://insights.sbomify.com/ALBA-2021-2573/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2021:2573

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