# s390/ap: use generic driver_override infrastructure

CVE record · `CVE-2026-53116`

- **Identifiers:** `CVE-2026-53116`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Jun 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Jun 2026, 16:30 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: `d38a87d7c0643db61e7a3bfc3ebeea2dc2568f7e to before 8f2eca0570438b94602da1297353eb7b10dcb6cb` (git)
  - affected: `d38a87d7c0643db61e7a3bfc3ebeea2dc2568f7e to before 81d6f7c3a70b10ff757ee8b5f8114a190871cf1e` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.19`
  - unaffected: `before 6.19` (semver)
  - unaffected: `7.0.10 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 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 s390 AP bus driver has a race condition in its driver_override handling that can lead to a potential use-after-free when AP masks are updated. The source gives few details on who can trigger it. Upgrade to Linux kernel 7.0.10 or later in the 7.0 series, or 7.1 or later, since 6.19 is affected.

Written 17 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 5th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Jun 2026, 16:30 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-53116)
- 24 Jun 2026, 17:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-53116)

## Sources

- [CVE List: CVE-2026-53116](https://www.cve.org/CVERecord?id=CVE-2026-53116)
- [NVD: CVE-2026-53116](https://nvd.nist.gov/vuln/detail/CVE-2026-53116)

### References from the CNA

- <https://git.kernel.org/stable/c/8f2eca0570438b94602da1297353eb7b10dcb6cb>
- <https://git.kernel.org/stable/c/81d6f7c3a70b10ff757ee8b5f8114a190871cf1e>

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 (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-53116>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-53116/>. Everything for agents: <https://agentprime.io/llms.txt>.
