{"metadata": {"vulnerability": "CVE-2026-99427", "count": 11, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 6}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.414Z", "date_only": false, "value": "2026-09-25T10:25:14.414Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99427", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:40:37.965Z", "date_only": false, "value": "2026-11-19T14:40:37.965Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99427", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:40:37.965Z", "date_only": false, "value": "2026-11-19T14:40:37.965Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99427", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:40:37.965Z", "date_only": false, "value": "2026-11-19T14:40:37.965Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99427", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T15:17:55Z", "date_only": false, "value": "2026-11-19T15:17:55Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-M53F-G3CV-WV3Q", "record": "GHSA-M53F-G3CV-WV3Q", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:17:55.777Z", "date_only": false, "value": "2026-11-19T15:17:55.777", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99427", "record": "FKIE_CVE-2026-99427", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:17:55.777Z", "date_only": false, "value": "2026-11-19T15:17:55.777", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99427", "record": "FKIE_CVE-2026-99427", "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-M53F-G3CV-WV3Q", "record": "GHSA-M53F-G3CV-WV3Q", "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-M53F-G3CV-WV3Q", "record": "GHSA-M53F-G3CV-WV3Q", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T16:05:19.154Z", "date_only": false, "value": "2026-11-19T16:05:19.154935Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117643956608405202", "record": "CVE-2026-99427", "field": "creation_timestamp", "uuid": "7b237ea0-bb14-4538-ac74-b742c81ab455", "content": "CVE-2026-99427 smb: client: fix OOB last_entry pointer from unbounded LastNameOffset In the Linux kernel, the following vulnerability has been resolved:\nsmb: client: fix OOB last_entry pointer from unbounded LastNameOffset\nCIFSFindFirst() and CIFSFindNext() locate the last entry of aTRANS2_FIND_FIRST2 or TRANS2_FIND_NEXT2 response by adding theLastNameOffset of the response parameters to the start of the dataarea, and store the result in psrch_inf-&gt;last_entry. MS-CIFS 2.2.6.2.2defines that offset as the offset of the entry's file name; the clientfollows the reading of NT and Samba servers, which point it at theentry. LastNameOffset is only checked against CIFSMaxBufSize, whichsays nothing about the response actually received: validate_t2() letsthe data area start up to 1024 bytes into the buffer, and SendReceive()copies at most CIFSMaxBufSize + MAX_CIFS_HDR_SIZE bytes of a response,16468 by default, into a cifs_request allocation of CIFSMaxBufSize +MAX_SMB2_HDR_SIZE bytes, 16588 by default. The pointer itself cantherefore be placed anywhere from the end of the received data to 820bytes past the end of the allocation.\nThe read through that pointer is far larger than its displacement.find_cifs_entry() hands last_entry to cifs_save_resume_key() after everyFindNext and after the FindFirst of a search rewind, andcifs_fill_dirent() takes the length of the name from the entry itself: a__le32 FileNameLength for most levels, a __u8 forSMB_FIND_FILE_INFO_STANDARD, and for SMB_FIND_FILE_UNIX the result of ascan for the terminating NUL over up to PATH_MAX + 1 UTF-16 units. Thename is recorded as the resume name of the search, and the nextCIFSFindNext() rejects only a recorded length of PATH_MAX or more beforecopying the name into the ResumeFileName of its request and sending itwith the resume key taken from the same entry: up to 4 KiB of memoryfrom past the end of the allocation leaks to the server, and forSMB_FIND_FILE_UNIX the NUL scan runs about twice as far before thelength is even known. The entry does not have to lie outside theresponse for that either: a maximal response ends about 120 bytes beforethe end of the allocation, so an entry in its last bytes with a namejust under PATH_MAX has nearly all of that name copied from past theallocation.\nIt needs nothing unusual from the client: a FindNext response thatreports no entries and does not end the search makes find_cifs_entry()send the next FindNext at once, carrying whatever was parsed atLastNameOffset, and a search rewind can do the same after itsFindFirst. SMB1 is not negotiated by default: this takes a maliciousor compromised server, a mount of it with an explicit vers=1.0, whichCONFIG_CIFS_ALLOW_INSECURE_LEGACY (default y) permits, and a directorylisting on that mount.\nWith KASAN enabled, a response that places the last entry past thebuffer, with a large DataOffset and a LastNameOffset near the end ofits range, gives:\n ================================================================== BUG: KASAN: slab-out-of-bounds in cifs_save_resume_key.isra.0+0x7aa/0x7f0 Read of size 4 at addr ffff88807b55c33b by task ls/83\n CPU: 1 UID: 0 PID: 83 Comm: ls Not tainted 7.3.0-rc4-00457-gf14572c203d5 #69 PREEMPT(lazy) Call Trace:  &lt;TASK&gt;  kasan_report+0xdf/0x1a0  cifs_save_resume_key.isra.0+0x7aa/0x7f0  cifs_readdir+0x1ed6/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 0 at 19.317556s:  cifs_buf_get+0x36/0x90  smb_init+0x4f/0x110  CIFSFindNext+0xf7/0x14c0  cifs_readdir+0xf51/0x29c0\n The buggy address belongs to the object at ffff88807b558000  which belongs to the cache cifs_request of size 16588 The buggy address is located 623 bytes to the right of  allocated 16588-byte region [ffff88807b558000, ffff88807b55c0cc) ==================================================================\nThe four bytes read there are the FileNameLength of the entry, whichcifs_fill_dirent() tak---truncated---\nhttps://www.cve.org/CVERecord?id=CVE-2026-99427https://git.kernel.org/stable/c/9bb37c10bbd57a4a2b7fa61f7c4af479225d0c11https://git.kernel.org/stable/c/daee49d7a51f1edb062581d49684c9cbfb3d7dc9https://git.kernel.org/stable/c/d6074ea8379b4bee953883f3bfa684cbc284eeebhttps://git.kernel.org/stable/c/570c783a96f054dd3ac409a92772e9afb705d21c#kernel #Linux#CVE_2026_99427#bot", "url": "https://infosec.exchange/users/cve/statuses/117643956608405202"}, {"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-99427", "record": "DEBIAN-CVE-2026-99427", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T05:55:24.255Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:40:37.965Z", "date_only": false, "value": "2026-11-19T14:40:37.965Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99427", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:40:37.965Z", "date_only": false, "value": "2026-11-19T14:40:37.965Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99427", "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": 54886.290619, "hours": 15.24619183861111, "days": 0.635257993275463, "min_seconds": 54886.290619, "max_seconds": 54886.290619, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:40:37.965Z", "date_only": false, "value": "2026-11-19T14:40:37.965Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99427", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T05:55:24.255Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
