Description
In the Linux kernel, the following vulnerability has been resolved:
9p: fix access mode flags being ORed instead of replaced
Since commit 1f3e4142c0eb ("9p: convert to the new mount API"), v9fs_apply_options() applies parsed mount flags with |= onto flags already set by v9fs_session_init(). For 9P2000.L, session_init sets V9FS_ACCESS_CLIENT as the default, so when the user mounts with "access=user", both bits end up set. Access mode checks compare against exact values, so having both bits set matches neither mode.
This causes v9fs_fid_lookup() to fall through to the default switch case, using INVALID_UID (nobody/65534) instead of current_fsuid() for all fid lookups. Root is then unable to chown or perform other privileged operations.
Fix by clearing the access mask before applying the user's choice.
Metrics
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1f3e4142c0eb178089ea0cbc97506a061470ad27, < b8f037e87a083291190204b959cda417aaf01058; >= 1f3e4142c0eb178089ea0cbc97506a061470ad27, < da2346a48a5a1fed86c3fe3d73c0b60e7b3027c9 |
| Linux | Linux | 6.19 |
References
Timeline
- Published
- Jun 9, 2026
- Last modified
- Jul 23, 2026
- NVD status
- Analyzed