CVE-2026-99181

autofs: ignore notification errors from a replaced pipe

State
Published
Severity
Not scored
Published
Oct 28, 2026
Updated
Oct 30, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

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

autofs: ignore notification errors from a replaced pipe

autofs_notify_daemon() takes a reference to the current notification pipe under wq_mutex, then drops the mutex before writing the request. The write can block while the daemon enters catatonic mode and installs a replacement pipe.

If the old pipe's reader is then closed, the delayed write returns -EPIPE and the generic error path enters catatonic mode again. That transition acts on the current superblock state, closes the replacement pipe, and releases the new daemon generation's wait queues.

Only enter catatonic mode when the pipe which failed is still the current pipe. Factor the already-locked transition so the identity check and state change are atomic with respect to another replacement.

This was reproduced on v7.3-rc5-337-gff47652a4b66c in a local QEMU guest. An unprivileged UID 65534 lookup filled the old packet pipe before a normal CATATONIC/SETPIPEFD restart. On the unmodified kernel, the new pipe received HUP and both a pending victim lookup and a later lookup failed with ENOENT in two out of two fresh-mount runs.

With this change, the new pipe remained active, received an intact 304-byte request, and both victim lookups completed in two out of two runs. Normal lookup and restart-without-a-blocked-writer controls passed. No KASAN, oops, refcount, or lock diagnostic was observed. A source reproducer and complete local logs are available privately on request.

The demonstrated impact is limited to denial of a shared autofs service during a legitimate daemon restart. No memory corruption, information leak, privilege escalation, or code execution primitive was observed.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 8d7b48e0bc5fa01a818eac713d4cb0763090cd0e to before 95ba5de229c1875e836f10646c4e6c454d560060Affected
  • 8d7b48e0bc5fa01a818eac713d4cb0763090cd0e to before d3477ebdce74dc3bae404048258e70d7046c208aAffected
  • 8d7b48e0bc5fa01a818eac713d4cb0763090cd0e to before 6d2b8ad36e09e07993addd4ce92b578d3b13c8f8Affected
  • 8d7b48e0bc5fa01a818eac713d4cb0763090cd0e to before 35c2c4f3cf1403b058237c44000199a6c9a59273Affected
  • 8d7b48e0bc5fa01a818eac713d4cb0763090cd0e to before 8c8386ffc582155451f074f25759f665e626a850Affected
  • 8d7b48e0bc5fa01a818eac713d4cb0763090cd0e to before 1a177064f501ed4b67873a43aae5d5bdb18b3704Affected
  • 8d7b48e0bc5fa01a818eac713d4cb0763090cd0e to before fb296391f685d82dbb93621a970fb234cea45280Affected
  • 8d7b48e0bc5fa01a818eac713d4cb0763090cd0e to before 65676cd4203c0e41a94caf54080a7f0a95434bdaAffected
LinuxLinux
  • 2.6.28Affected
  • before 2.6.28Not affected
  • 5.10.273 through 5.10.*Not affected
  • 5.15.224 through 5.15.*Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.161 through 6.6.*Not affected
  • 6.12.115 through 6.12.*Not affected
  • 6.18.59 through 6.18.*Not affected
  • 7.2.13 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.