# CVE-2026-97505: PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store()

> Unprivileged local users can resize PCI BARs via sysfs without CAP_SYS_ADMIN, potentially causing driver disruption or privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-103724, BELL-CVE-2026-97505, DEBIAN-CVE-2026-97505, GHSA-6xm8-36mh-mxj7, UBUNTU-CVE-2026-97505

## What is CVE-2026-97505?

CVE-2026-97505 is a missing authorization 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:

PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store()

Currently, the __resource_resize_store() allows writing to the
resourceN_resize sysfs attribute to change a BAR's size without checking
for capabilities, currently relying only on the file access check.

Resizing a BAR modifies PCI device configuration and can disrupt active
drivers.  After the upcoming conversion to static attributes, it will also
trigger resource file updates via sysfs_update_groups().

Add a CAP_SYS_ADMIN check to prevent unprivileged users from performing BAR
resize operations.

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


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

Apply the vendor's patch.

## Is CVE-2026-97505 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97505 is a missing authorization 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-97505 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-97505/ (Markdown: https://insights.sbomify.com/CVE-2026-97505/index.md)
```

## Sources

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

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