Root Cause Analysis
1. Involved Files, Functions, Structs, and Fields
- Source Files:
- Functions:
- Structs and Fields:
2. Technical Mechanism and Triggering Sequence
-
VFS Inode Permission Flow:
During path lookup (e.g. path_openat() -> link_path_walk() -> may_lookup() -> lookup_inode_permission_may_exec()), VFS calls inode_permission(idmap, inode, mask).
In inode_permission():
retval = do_inode_permission(idmap, inode, mask);
if (unlikely(retval))
return retval;
...
return security_inode_permission(idmap, inode, mask);
No locks are held on struct inode (such as inode->i_rwsem or inode->i_lock) during standard path traversal and permission checking.
-
Kernfs Inode Refresh under Shared Reader Lock:
When do_inode_permission() invokes the filesystem's ->permission callback on a kernfs inode, kernfs_iop_permission() is executed:
down_read(&root->kernfs_iattr_rwsem);
kernfs_refresh_inode(kn, inode);
ret = generic_permission(&nop_mnt_idmap, inode, mask);
up_read(&root->kernfs_iattr_rwsem);
In kernfs_refresh_inode():
inode->i_mode = kn->mode;
attrs = kernfs_iattrs_noalloc(kn);
if (attrs)
set_inode_attr(inode, attrs);
kernfs_refresh_inode() performs plain, non-atomic writes to inode->i_mode (and other attributes such as UID, GID, timestamps, and i_nlink) to synchronize the VFS inode with the persistent attributes stored in struct kernfs_node.
-
Concurrency and Synchronization Defect:
Because neither access uses atomic primitives or acquire/release annotations (READ_ONCE() / WRITE_ONCE()), and no mutual exclusion lock guards struct inode::i_mode across inode_permission(), KCSAN detects and reports a data race between kernfs_refresh_inode() and selinux_inode_permission().