{"metadata": {"vulnerability": "CVE-2026-99526", "count": 11, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 6}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.420Z", "date_only": false, "value": "2026-09-25T10:25:14.420Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99526", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:44:38.249Z", "date_only": false, "value": "2026-11-19T14:44:38.249Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99526", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:44:38.249Z", "date_only": false, "value": "2026-11-19T14:44:38.249Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99526", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:44:38.249Z", "date_only": false, "value": "2026-11-19T14:44:38.249Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99526", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T15:18:08Z", "date_only": false, "value": "2026-11-19T15:18:08Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-VWG2-524X-VX4V", "record": "GHSA-VWG2-524X-VX4V", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:18:08.263Z", "date_only": false, "value": "2026-11-19T15:18:08.263", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99526", "record": "FKIE_CVE-2026-99526", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:18:08.263Z", "date_only": false, "value": "2026-11-19T15:18:08.263", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99526", "record": "FKIE_CVE-2026-99526", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-19T15:31:27Z", "date_only": false, "value": "2026-11-19T15:31:27Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-VWG2-524X-VX4V", "record": "GHSA-VWG2-524X-VX4V", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:31:27Z", "date_only": false, "value": "2026-11-19T15:31:27Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-VWG2-524X-VX4V", "record": "GHSA-VWG2-524X-VX4V", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T17:12:07.360Z", "date_only": false, "value": "2026-11-19T17:12:07.360955Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117644219301325069", "record": "CVE-2026-99526", "field": "creation_timestamp", "uuid": "73e7d671-ed23-43cc-b567-7dbb0c5fef09", "content": "CVE-2026-99526 smb: client: fix use-after-free infoleak via the readdir resume name In the Linux kernel, the following vulnerability has been resolved:\nsmb: client: fix use-after-free infoleak via the readdir resume name\nCIFSFindNext() copies the resume name that cifs_save_resume_key()recorded from the last entry of the previous response into its request;psrch_inf-&gt;presume_name points into the response buffer that entry camefrom, and nothing ever clears it. find_cifs_entry() records a newname only from a response with a usable last entry, and cifs_readdir()only from an entry it walks to, so a response that carries no entriesand leaves last_entry NULL, because CIFSFindFirst() or CIFSFindNext()rejected LastNameOffset, refreshes neither and presume_name keepspointing into the previous response. That buffer has already beenreleased: by CIFSFindNext() before it installs the new response, or byfind_cifs_entry() when it rewinds the search, which does not drop thename either and can then fail in initiate_cifs_search() before a newresponse replaces it. The next CIFSFindNext() then copies up toPATH_MAX - 1 bytes of the resume name out of the released buffer intoits request and sends them to the server: a use-after-free readthat leaks kernel memory to a malicious or compromised server, whichcan provoke it with a single FindNext response that carries no entriesand a LastNameOffset above CIFSMaxBufSize, which is all the existingcheck rejects.\nWith KASAN enabled, a server that answers a listing that way gives:\n CIFS: VFS: ignoring corrupt resume name ================================================================== BUG: KASAN: slab-use-after-free in CIFSFindNext+0x8ca/0x14c0 Read of size 4080 at addr ffff88807c823f98 by task ls/83\n CPU: 0 UID: 0 PID: 83 Comm: ls Tainted: G    B               7.3.0-rc4-00457-gf14572c203d5 #69 PREEMPT(lazy) Tainted: [B]=BAD_PAGE Call Trace:  &lt;TASK&gt;  kasan_report+0xdf/0x1a0  kasan_check_range+0x10f/0x1e0  __asan_memcpy+0x23/0x60  CIFSFindNext+0x8ca/0x14c0  cifs_readdir+0xf51/0x29c0  iterate_dir+0x1c0/0x570  __x64_sys_getdents64+0x133/0x270  do_syscall_64+0x109/0x5d0  entry_SYSCALL_64_after_hwframe+0x77/0x7f  &lt;/TASK&gt;\n Allocated by task 83 on cpu 1 at 13.497119s:  cifs_buf_get+0x36/0x90  smb_init+0x4f/0x110  CIFSFindNext+0xf7/0x14c0  cifs_readdir+0xf51/0x29c0\n Freed by task 83 on cpu 0 at 13.584018s:  cifs_buf_release+0x41/0x80  CIFSFindNext+0xfce/0x14c0  cifs_readdir+0xf51/0x29c0\n The buggy address is located 16280 bytes inside of  freed 16588-byte region [ffff88807c820000, ffff88807c8240cc) ==================================================================\nThe same memcpy() first reads past the end of that object while it isstill live, a slab-out-of-bounds read that the following patchesbound; that is the taint the report above carries.\nSMB1 is not negotiated by default; reaching this code requires anexplicit vers=1.0 mount.\nClear presume_name and resume_name_len whenever a new response isinstalled and when the rewind path releases the search buffer, so thatthe name never outlives the buffer it points into, and resetresume_key with them, since it was taken from the same entry and wouldotherwise be sent with an empty name. A response without a usablelast entry then continues the search with an empty resume name ratherthan a stale one; CIFSFindNext() skips the copy of a zero-length nameso that it never runs on the NULL pointer.\nThe next patch in the series leaves last_entry NULL for a responsethat carries no entries, and bounds LastNameOffset against thereceived response rather than against CIFSMaxBufSize. Responses thatare given a last entry today then take the path fixed here, so thatpatch must not be applied without this one.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99526https://git.kernel.org/stable/c/8c8f8029fe07634b626e96472b584b29a33993b8https://git.kernel.org/stable/c/6c4c12b0fadcb71e4e6616e6c1ca529c772f2a15https://git.kernel.org/stable/c/a3481ed0aea2fc41a6d892a586b6eb7a97662034https://git.kernel.org/stable/c/59131dd72f62b198fc9ea1489ad9d3573154f684#kernel #Linux#CVE_2026_99526#bot", "url": "https://infosec.exchange/users/cve/statuses/117644219301325069"}, {"timestamp": "2026-11-19T19:09:23.206Z", "date_only": false, "value": "2026-11-19T19:09:23.206732+00:00", "kind": "other", "label": "Updated", "source": "debian_tracker \u00b7 DEBIAN-CVE-2026-99526", "record": "DEBIAN-CVE-2026-99526", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T04:13:08.882Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:44:38.249Z", "date_only": false, "value": "2026-11-19T14:44:38.249Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99526", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:44:38.249Z", "date_only": false, "value": "2026-11-19T14:44:38.249Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99526", "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": 48510.633281, "hours": 13.47517591138889, "days": 0.561465662974537, "min_seconds": 48510.633281, "max_seconds": 48510.633281, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:44:38.249Z", "date_only": false, "value": "2026-11-19T14:44:38.249Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99526", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T04:13:08.882Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
