GHSA-g854-mv2r-2r5h
Record from GitHub Advisory Database · Published July 24, 2023
A possible unauthorized memory access flaw was found in the Linux kernel's cpu_entry_area mapping of X86 CPU data to memory, where a user may guess the location of exception stacks or other important data. Based on the previous CVE-2023-0597, the 'Randomize per-cpu entry area' feature was implemented in /arch/x86/mm/cpu_entry_area.c, which works through the init_cea_offsets() function when KASLR is enabled. However, despite this feature, there is still a risk of per-cpu entry area leaks. This issue could allow a local user to gain access to some important data with memory in an expected location and potentially escalate their privileges on the system.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux-qemu-6.12 | Chainguard | 6.12.71-r0 |
| linux-vmware-6.12 | Chainguard | 6.12.71-r0 |
| linux-qemu-6.18 | Chainguard | 6.18.10-r0 |
| linux-vmware-6.18 | Chainguard | 6.18.10-r0 |
| linux-qemu-melange | Chainguard | 6.18.16-r0 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| chainguard | linux-gcp-generic | * |
| chainguard | linux-vmware-generic | * |
| chainguard | linux-gcp-6.12 | * |
| chainguard | linux-qemu-6.12 | 0 |
| chainguard | linux-aws-6.18 | * |
| chainguard | linux-vmware-6.12 | 0 |
| chainguard | linux-qemu-rc | * |
| chainguard | linux-qemu-6.18 | 0 |
| chainguard | linux-azure-6.18 | * |
| chainguard | linux-vmware-6.18 | 0 |
| chainguard | linux-qemu-melange | 0 |
| chainguard | linux | * |
| chainguard | linux-gcp-6.18 | * |
| chainguard | linux-aws-6.12 | * |
| chainguard | linux-qemu-generic | * |
| chainguard | linux-azure-6.12 | * |
| chainguard | linux-aws-generic | * |
| chainguard | linux-azure-generic | * |
Timeline
- Jul 24, 2023 CVE Published
- May 1, 2026 Security Advisory
- Aug 6, 2026 Distribution Patch
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln GHSA-g854-mv2r-2r5h
vulnetix vdb fixes GHSA-g854-mv2r-2r5hOr with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/GHSA-g854-mv2r-2r5h/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart