# PCI/sysfs: Add CAP_SYS_ADMIN check to \_\_resource_resize_store() CVE record · `CVE-2026-97505` - **Identifiers:** `CVE-2026-97505` - **State:** Confirmed - **Severity:** No CVSS score - **Critical:** No - **CNA:** Linux - **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md) - **Published:** 24 Sept 2026 - **Updated:** 30 Oct 2026 - **Reviewed by a person:** No Published by the CVE Program (CNA: Linux) at 24 Sept 2026, 16:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. ## Affected products, as the CNA wrote them - Vendor: Linux. Product: Linux. - affected: `91fa127794ac1c48069479b9d45eb4c7378c0e30 to before 0be4e21287e1e4865b9de498e1acc65b873f52f5` (git) - affected: `91fa127794ac1c48069479b9d45eb4c7378c0e30 to before d02dd7ce8e52b66b7d3b6eca2a7d81e7f5b10a62` (git) - affected: `91fa127794ac1c48069479b9d45eb4c7378c0e30 to before b722a607f858b9cd036075ea0efad553fb98e982` (git) - affected: `91fa127794ac1c48069479b9d45eb4c7378c0e30 to before cbf0628c0b7db86c5ce36451f088101546acbf1d` (git) - affected: `91fa127794ac1c48069479b9d45eb4c7378c0e30 to before 25ec7f57deceec633f27bc93b615f951e2ade814` (git) - Other versions: unaffected - Vendor: Linux. Product: Linux. - affected: `6.1` - unaffected: `before 6.1` (semver) - unaffected: `6.1.191 to 6.1.*, inclusive` (semver) - unaffected: `6.6.160 to 6.6.*, inclusive` (semver) - unaffected: `6.12.111 to 6.12.*, inclusive` (semver) - unaffected: `6.18.53 to 6.18.*, inclusive` (semver) - unaffected: `7.2 to *, inclusive` (original_commit_for_fix) - Other versions: affected ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The Linux kernel's PCI sysfs interface (resourceN_resize attribute) lacked a capability check, so writing to it to change a PCI BAR's size was allowed without CAP_SYS_ADMIN, relying only on normal file access permissions. The source does not describe a specific exploit path. Affected kernel versions are listed as ranges by commit, starting at 91fa127794ac1c48069479b9d45eb4c7378c0e30; the source lists 6.1 as affected, with fixed versions 6.1.191, 6.6.160, 6.12.111 and 6.18.53 and later in each series. Upgrade to a fixed stable kernel release for your series. No workaround is given. Written 12 Nov 2026. ## Not analysed yet We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter. ## Severity and exploitation No source has published a CVSS score for this record yet. - **CISA KEV:** Not listed. - **EPSS:** 0.0016, the 4th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline This record came from the full history of the CVE Program, published 24 Sept 2026. New records show when each source confirmed them. ## Sources - [CVE List: CVE-2026-97505](https://www.cve.org/CVERecord?id=CVE-2026-97505) - [NVD: CVE-2026-97505](https://nvd.nist.gov/vuln/detail/CVE-2026-97505) ### References from the CNA - - - - - Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description. ## Check whether this affects you This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run. - With the agentprime MCP server (), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: - As JSON: - Everything that needs attention now: --- The web page: . Everything for agents: .