# CVE-2026-98917: parisc: Increase kernel stack size to 32kb


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110699, BELL-CVE-2026-98917, DEBIAN-CVE-2026-98917, GHSA-2c7p-wf48-2qwx, UBUNTU-CVE-2026-98917

## What is CVE-2026-98917?

CVE-2026-98917 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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

parisc: Increase kernel stack size to 32kb

For 64-bit Linux kernels, increase the default kernel stack size
(THREAD_SIZE_ORDER) to 32 kB, in order to avoid kernel crashes which have been
triggered recently when building the debian vtk9 package with gcc 17:

stackcheck: kworker/u128:0 will most likely overflow kernel stack (sp:179a83af0, stk bottom-top:179a80000-179a84000)
Kernel panic - not syncing: low stack detected by irq handler - check messages
CPU: 2 UID: 0 PID: 30760 Comm: kworker/u128:0 Tainted: G W 6.18.46-dirty #1 NONE
Tainted: [W]=WARN
Hardware name: 9000/800/rp3440
Workqueue: writeback wb_workfn (flush-259:0)
Backtrace:
 [<000000004022f050>] show_stack+0x70/0x90
 [<000000004022378c>] dump_stack_lvl+0x124/0x190
 [<000000004022382c>] dump_stack+0x34/0x48
 [<000000004020212c>] vpanic+0x204/0x648
 [<00000000402025c4>] panic+0x54/0x58
 [<0000000040232230>] do_cpu_irq_mask+0x3f8/0x440
 [<0000000040227070>] intr_return+0x0/0xc

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


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

Upgrade to a fixed version.

## Is CVE-2026-98917 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98917 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98917 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-98917/ (Markdown: https://insights.sbomify.com/CVE-2026-98917/index.md)
```

## Sources

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

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