# CVE-2026-98249: arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc

> A missing argument in the ARM64 hibernation resume path causes a system hang when page poisoning is enabled, requiring local high-privilege access to trigger.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106455, BELL-CVE-2026-98249, DEBIAN-CVE-2026-98249, GHSA-fm6m-qcv7-63xp, UBUNTU-CVE-2026-98249

## What is CVE-2026-98249?

CVE-2026-98249 is a denial of service vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc

swsusp_arch_suspend_exit() reinstalls the restored kernel's hyp stub
vectors with an hvc, but never passes the arguments. x0 is not set to
HVC_SET_VECTORS and x1 is not set to the vector address, so the stub
dispatch falls through and returns without writing vbar_el2. EL2 is
left pointing at the trans_pgd copy of the vectors, a page that
swsusp_free() releases right after resume.

Set the arguments up the same way __hyp_set_vectors() does.

Without this fix, Vladimir was able to trigger a hang when resuming from
hibernation with CONFIG_PAGE_POISONING=y and page_poison=on.

## Which versions are affected by CVE-2026-98249?


## How do I fix CVE-2026-98249?

Apply the vendor's patch.

## Is CVE-2026-98249 being exploited?

There is no known exploitation of CVE-2026-98249 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98249 and fix it if it is affected.

What it is: CVE-2026-98249 is a denial of service vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98249 in the wild and no public exploit code.

Affected product: Linux. 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/CVE-2026-98249/ (Markdown: https://insights.sbomify.com/CVE-2026-98249/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98249
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98249
- OSV: https://osv.dev/vulnerability/CVE-2026-98249

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