# ALEA-2021:3072: vulkan bug fix and enhancement update

> This update rebases Vulkan components to fix bugs and enhance functionality, with no specific security vulnerability details provided.

- **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:** 10 Aug 2021

## What is ALEA-2021:3072?

ALEA-2021:3072 is a vulnerability in spirv-tools-devel, published on 10 Aug 2021. 

### Official description

The vulkan packages contain the reference ICD loader and validation layers for Vulkan, a graphics and compute API for cross-platform access to modern GPUs.

Bug Fix(es) and Enhancement(s):

* Rebase vulkan-loader in 8.5 (BZ#1952989)

* Rebase vulkan-headers in 8.5 (BZ#1952990)

* Rebase spirv-headers in 8.5 (BZ#1952991)

* Rebase spirv-tools in 8.5 (BZ#1952992)

* Rebase glslang in 8.5 (BZ#1952993)

* Rebase vulkan-tools in 8.5 (BZ#1952994)

* Rebase vulkan-validation-layers in 8.5 (BZ#1952995)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `spirv-tools-devel` | AlmaLinux:8 | All versions | 2021.2-1.20210619.git5dd2f76.el8_4 |
| `spirv-tools-libs` | AlmaLinux:8 | All versions | 2021.2-1.20210619.git5dd2f76.el8_4 |

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

Upgrade to a fixed version.

## Is ALEA-2021:3072 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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