# CVE-2026-99265: io_uring/openclose: keep the lock in io_pipe_fixed()

Status: published. Published: 2026-11-03. Updated: 2026-11-03.

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

io_uring/openclose: keep the lock in io_pipe_fixed()

io_pipe_fixed() installs both ends of the pipe in the fixed file table,
drops ->uring_lock, and copies the slot numbers to the application. If
that faults, it takes the lock again and removes whatever is in these
slots.

If the request is run by io-wq the lock really is dropped in between, and
the slots are visible to everybody else. By the time the error path gets
to them, they may have been closed and reused, by IORING_OP_CLOSE and a
direct open or accept, or by IORING_REGISTER_FILES_UPDATE. Then a file is
removed from the table that has nothing to do with the failed request.

Do the copy with the lock held. Faulting in user memory under
->uring_lock is fine, the registration paths do it all the time.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 53db8a71ecb42c2ec5e9c6925269a750255f9af5; < b4b7b2d19dab611f3cf3d052aa19278e7e4c4683 (affected, git); ≥ 53db8a71ecb42c2ec5e9c6925269a750255f9af5; < 7299a32764ab875443b58581d929027954dcf24c (affected, git). Source: CNA: Linux
- Linux / Linux: 6.16 (affected); ≥ 0; < 6.16 (unaffected, semver); ≥ 6.18.60; ≤ 6.18.* (unaffected, semver); ≥ 7.2.14; ≤ 7.2.* (unaffected, semver). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/b4b7b2d19dab611f3cf3d052aa19278e7e4c4683 (CNA: Linux)

- https://git.kernel.org/stable/c/7299a32764ab875443b58581d929027954dcf24c (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99265; retrieved 2026-11-03; source updated 2026-11-03

Revision: 8af349741f5dee173df902882b92813c9f98e6bb601c3f759dda58dc3d804e61

Canonical: https://y2.dev/cve/CVE-2026-99265

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.