{"metadata": {"vulnerability": "CVE-2026-99416", "count": 11, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 6}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.413Z", "date_only": false, "value": "2026-09-25T10:25:14.413Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99416", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:40:14.495Z", "date_only": false, "value": "2026-11-19T14:40:14.495Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99416", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:40:14.495Z", "date_only": false, "value": "2026-11-19T14:40:14.495Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99416", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:40:14.495Z", "date_only": false, "value": "2026-11-19T14:40:14.495Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99416", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T15:17:54Z", "date_only": false, "value": "2026-11-19T15:17:54Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-QH63-HQ2W-9GM3", "record": "GHSA-QH63-HQ2W-9GM3", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:17:54.357Z", "date_only": false, "value": "2026-11-19T15:17:54.357", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99416", "record": "FKIE_CVE-2026-99416", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:17:54.357Z", "date_only": false, "value": "2026-11-19T15:17:54.357", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99416", "record": "FKIE_CVE-2026-99416", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-19T15:31:24Z", "date_only": false, "value": "2026-11-19T15:31:24Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-QH63-HQ2W-9GM3", "record": "GHSA-QH63-HQ2W-9GM3", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:31:24Z", "date_only": false, "value": "2026-11-19T15:31:24Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-QH63-HQ2W-9GM3", "record": "GHSA-QH63-HQ2W-9GM3", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T15:45:48.019Z", "date_only": false, "value": "2026-11-19T15:45:48.019296Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117643879877441211", "record": "CVE-2026-99416", "field": "creation_timestamp", "uuid": "33854b89-645a-4a70-bc28-996260d0c230", "content": "CVE-2026-99416 ovl: read the nlink xattr of every indexed non-dir In the Linux kernel, the following vulnerability has been resolved:\novl: read the nlink xattr of every indexed non-dir\nWith nfs_export=on, data written through a file handle to a lower file,i.e. a file that exists only in a lower layer of the overlay, can belost on the next mount. A lookup of the file by name then returns -EIO.Also, a file with one name reports st_nlink 2 once it has been copied tothe upper layer. After such a file is removed, its file handle can stillopen it until the next mount.\nBefore a lower file is changed for the first time, overlayfs copies itto the writable upper layer. This is called copy up.\nThe index directory is $workdir/index, where $workdir is the directorygiven by the workdir= option. Each entry is named after the file handleof a lower inode, so that overlayfs can get from the handle to thecopied up inode.\nWith nfs_export=on, copy up indexes every non-directory: it copies thefile to an entry in the index directory and then hard links that entryinto the upper directory. The index entry is an extra link to the upperinode, so overlayfs stores the link count that users should see in theoverlay.nlink xattr.\nA file can also be opened by handle, either by an NFS client or by aprocess with CAP_DAC_READ_SEARCH calling open_by_handle_at(). If thefile is not in the dcache, its overlay dentry is disconnected, i.e. ithas no parent yet. Copy up then creates the index entry but no hard linkin the upper directory. The index entry has i_nlink 1 and holds the onlycopy of the data written to the file.\novl_get_nlink() reads the stored count. Its caller passes a default,which the function returns if there is no stored count. If the lowerinode has i_nlink 1, the function returns the default without readingthe xattr. That was correct as long as only lower files with multiplelinks were indexed.\nOn the next mount, ovl_verify_index() looks for orphans, i.e. indexentries of files whose last name was removed. For an index entry withi_nlink 1, it passes a default of 0 to ovl_get_nlink() and treats aresult of 0 as an orphan. Here the lower inode also has i_nlink 1, sothe result is the default. ovl_indexdir_cleanup() then replaces theentry with a whiteout, which in the index marks a file as deleted. Thewritten data is lost.\nA lookup by name then returns -EIO, because a whiteout as the indexentry of a lower file that still exists is a bad index.\novl_get_inode() gets the wrong count the same way. Its default is thei_nlink of the upper inode, which includes the index entry, so a copiedup file with one name reports st_nlink 2.\nWhen that name is removed, the count drops to 1 rather than 0.ovl_nlink_end() replaces the index entry with a whiteout only at a countof 0, so the entry stays, and the handle of the removed file still opensit.\nReproduced by writing through open_by_handle_at() to an uncached lowerfile with one link. After a remount the data was lost, and the namereturned EIO.\nFix this by adding an argument to ovl_get_nlink() that says whether thecaller found an index entry, and by skipping the xattr only if thecaller found none.\nKnown gaps:- An index entry that a kernel without this patch left behind for a  removed file now stays, and the handle of that file keeps working. The  entry has i_nlink 1 and a stored count of 1, just like the entry of a  file that was only written by handle. Without this patch, the next  mount treated it as an orphan.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99416https://git.kernel.org/stable/c/07b000b5b458723ca85d67dbbe5f6359c0202cfchttps://git.kernel.org/stable/c/9b50f28c22c948b0c134d5c5dbd62ea0ada97fc3https://git.kernel.org/stable/c/ffe508adf85acdd57db01a234161e795b7403062https://git.kernel.org/stable/c/eb644ed5c6d9afdb1554c41cef1f39d150fbc554#kernel #Linux#CVE_2026_99416#bot", "url": "https://infosec.exchange/users/cve/statuses/117643879877441211"}, {"timestamp": "2026-11-20T05:12:10.083Z", "date_only": false, "value": "2026-11-20T05:12:10.083058+00:00", "kind": "other", "label": "Updated", "source": "debian_tracker \u00b7 DEBIAN-CVE-2026-99416", "record": "DEBIAN-CVE-2026-99416", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T05:56:12.197Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:40:14.495Z", "date_only": false, "value": "2026-11-19T14:40:14.495Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99416", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:40:14.495Z", "date_only": false, "value": "2026-11-19T14:40:14.495Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99416", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 54957.702872, "hours": 15.266028575555556, "days": 0.6360845239814815, "min_seconds": 54957.702872, "max_seconds": 54957.702872, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:40:14.495Z", "date_only": false, "value": "2026-11-19T14:40:14.495Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99416", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T05:56:12.197Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
