{"id":"AZL-115396","summary":"CVE-2026-99616 affecting package kernel 6.6.161.1-1","details":"In the Linux kernel, the following vulnerability has been resolved:\n\novl: look up the index by the decoded origin\n\nA file opened by file handle on an overlay with nfs_export=on can show\nthe stale lower data of a file that was copied up to the upper layer.\nWhile the file opened this way stays in the inode cache, a lookup of the\ncopied up file by path fails with ESTALE for all users. The open can\nalso succeed for a file that was removed, where it has to fail with\nESTALE. This happens with a handle that has one byte changed. The handle\ncomes from an NFS client, or from a process that calls\nopen_by_handle_at() with CAP_DAC_READ_SEARCH in the initial user\nnamespace.\n\nWhen a file in a lower layer is about to be modified, overlayfs first\ncopies it to the upper layer (copy up). With nfs_export=on, each copy up\nalso creates an entry in the index directory, a directory that overlayfs\nkeeps for itself on the upper filesystem.\n\nThe handle of an overlay file that comes from a lower layer wraps the\nhandle of its lower inode. Overlayfs calls this lower inode the origin.\nThe overlay handle stays valid after a copy up.\n\nTo decode such a handle, ovl_lower_fh_to_d() first decodes the wrapped\nhandle to the origin. If no overlay inode is cached for the origin, it\nlooks in the index directory:\n\n- An index entry there leads to the upper file.\n- A whiteout, the marker that overlayfs uses for a removed file, means\n  that the overlay file was removed.\n\nThe name of an index entry is the handle that copy up encoded for the\norigin, as a hex string.\n\novl_lower_fh_to_d() builds the name for this lookup from the bytes that\nthe caller passed in. But handles with different bytes can decode to the\nsame inode:\n\n- Overlayfs ignores some flag bits of the handle.\n- A lower filesystem can accept a different fid type, extra bytes, or\n  generation 0 for any generation.\n\nSuch a handle decodes to the origin but misses the index entry or the\nwhiteout. So the decode returns an overlay inode that has only the lower\nfile.\n\nWhile that inode is cached, a path lookup of a copied up file fails with\nESTALE, since the upper file that the lookup finds does not match the\ncached inode, which has none.\n\nReproduced on tmpfs and on ext4 with open_by_handle_at(), after a copy\nup and a mount cycle. A handle in which one flag bit, the fid type, the\nlength or the generation was changed read the old lower data, and path\nlookups returned ESTALE.\n\nFix this by re-encoding the decoded origin and building the index name\nfrom that handle.","modified":"2026-11-21T14:17:23.710817143Z","published":"2026-11-20T06:17:54Z","upstream":["CVE-2026-99616"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99616"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.161.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-115396.json"}}],"schema_version":"1.9.2"}