# CVE-2026-97503: genirq/proc: Size interrupt directory names for 10-digit interrupt numbers

> A buffer overflow in the Linux kernel's proc filesystem allows local attackers to cause denial of service or execute code via large interrupt numbers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-103544, BELL-CVE-2026-97503, DEBIAN-CVE-2026-97503, GHSA-7j5w-cr4g-jjc9, UBUNTU-CVE-2026-97503

## What is CVE-2026-97503?

CVE-2026-97503 is a memory corruption vulnerability in Linux, published on 24 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:

genirq/proc: Size interrupt directory names for 10-digit interrupt numbers

/proc/irq/<n>/ directory names are built in `char name[10]` buffers
with `sprintf(name, "%u", irq)`.

Ten-digit IRQ numbers already need 11 bytes including the trailing NUL, and
current sparse-IRQ configurations allow interrupt numbers in that range.

Size the temporary name buffer for the current decimal form and switch
to bounded formatting when creating or removing the proc entry.

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


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

Apply the vendor's patch.

## Is CVE-2026-97503 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97503 is a memory corruption vulnerability in Linux, published on 24 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-97503 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-97503/ (Markdown: https://insights.sbomify.com/CVE-2026-97503/index.md)
```

## Sources

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

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