{"id":"AZL-110828","summary":"CVE-2026-98990 affecting package kernel 6.6.157.1-1","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: check a submount for references right before unmounting it\n\nshrink_submounts() and mark_mounts_for_expiry() first collect all the\nmounts they are allowed to unmount and then unmount them.\n\nWhether a mount is busy is decided by propagate_mount_busy() on the\ntree. But unmounting the first mount changes the tree that the second\none propagates into. propagate_umount()\nmoves a surviving overmount off a copy it unmounts and mounts it where\nthe copy was mounted. If that's where the propagated copy of the second\nvictim is looked up the overmount becomes a candidate of the second\numount_tree(). It's childless and so trim_one() commits it without\nlooking at its reference count.\n\nSo a synchronous umount pulls out a busy mount that is in use somewhere\nelse and marks it MNT_SYNC_UMOUNT while it has users:\n\n  umount2(/tmp/plshrink/p1, 0) = 0 errno 0\n  cwd is (unreachable)\n\nThe same two umounts requested one after the other fail with EBUSY.\nThis needs a mount with MNT_SHRINKABLE, i.e., automounted submounts of\nNFS, AFS and CIFS or the tracefs mount below debugfs. Bind mounts\ninherit the flag.\n\nCheck each mount right before it is unmounted under the same hold of\nnamespace_sem and mount_lock as the umount itself. Make sure that the\nalgorithm stays linear.","modified":"2026-10-25T05:30:37Z","published":"2026-10-23T13:17:20Z","upstream":["CVE-2026-98990"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98990"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.157.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-110828.json"}}],"schema_version":"1.9.0"}