# CVE-2026-90290: arm64: hibernate: Restore DAIF state on error

> A flaw in the Linux kernel arm64 hibernation code fails to restore interrupt state on error, potentially causing a denial of service.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-103001, BELL-CVE-2026-90290, DEBIAN-CVE-2026-90290, GHSA-49wg-x228-h4jh, UBUNTU-CVE-2026-90290

## What is CVE-2026-90290?

CVE-2026-90290 is a denial of service vulnerability in Linux, published on 17 Sep 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: Restore DAIF state on error

Sashiko AI has reported that if swsusp_mte_save_tags() for some reason
fails we return from swsusp_arch_suspend() with DAIF being masked -
that is not what we'd expect. Restore the saved DAIF state before
returning from the error path.

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


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

Apply the vendor's patch.

## Is CVE-2026-90290 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90290 is a denial of service vulnerability in Linux, published on 17 Sep 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-90290 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-90290/ (Markdown: https://insights.sbomify.com/CVE-2026-90290/index.md)
```

## Sources

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

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