# ALEA-2021:3065: libwacom bug fix and enhancement update

> This update provides bug fixes and enhancements for the libwacom library, improving tablet support and configuration on AlmaLinux systems.

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

## What is ALEA-2021:3065?

ALEA-2021:3065 is a vulnerability in libwacom-devel, published on 10 Aug 2021. 

### Official description

The libwacom packages contain a library that provides access to a tablet
model database. The libwacom packages expose the contents of this database to
applications, allowing for tablet-specific user interfaces. The libwacom
packages allow the GNOME tools to automatically configure screen mappings
and calibrations, and provide device-specific configurations.

Bug Fix(es) and Enhancement(s):

* Lenovo: Upstream libwacom fix for X1Y6 (AlmaLinux) (BZ#1965300)

## Which versions are affected by ALEA-2021:3065?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libwacom-devel` | AlmaLinux:8 | All versions | 1.6-2.1.el8_4 |

## How do I fix ALEA-2021:3065?

Upgrade to a fixed version.

## Is ALEA-2021:3065 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALEA-2021:3065 is a vulnerability in libwacom-devel, published on 10 Aug 2021. 
Exploitation: There is no known exploitation of ALEA-2021:3065 in the wild and no public exploit code.

Affected product: libwacom-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/ALEA-2021-3065/ (Markdown: https://insights.sbomify.com/ALEA-2021-3065/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALEA-2021:3065

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