{"metadata": {"vulnerability": "CVE-2026-99430", "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-99430", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:41:03.138Z", "date_only": false, "value": "2026-11-19T14:41:03.138Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99430", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:41:03.138Z", "date_only": false, "value": "2026-11-19T14:41:03.138Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99430", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:41:03.138Z", "date_only": false, "value": "2026-11-19T14:41:03.138Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99430", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T15:17:56Z", "date_only": false, "value": "2026-11-19T15:17:56Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-7VHF-83C4-H86C", "record": "GHSA-7VHF-83C4-H86C", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:17:56.240Z", "date_only": false, "value": "2026-11-19T15:17:56.240", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99430", "record": "FKIE_CVE-2026-99430", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:17:56.240Z", "date_only": false, "value": "2026-11-19T15:17:56.240", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99430", "record": "FKIE_CVE-2026-99430", "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-7VHF-83C4-H86C", "record": "GHSA-7VHF-83C4-H86C", "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-7VHF-83C4-H86C", "record": "GHSA-7VHF-83C4-H86C", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T16:07:20.246Z", "date_only": false, "value": "2026-11-19T16:07:20.246276Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117643964547882294", "record": "CVE-2026-99430", "field": "creation_timestamp", "uuid": "67b1de9d-452a-4db8-bc61-ec116c73eeaf", "content": "CVE-2026-99430 ocfs2: fix chunk number of the first chunk in a local quota file In the Linux kernel, the following vulnerability has been resolved:\nocfs2: fix chunk number of the first chunk in a local quota file\nMounting a crafted OCFS2 image can corrupt kernel memory.  When thelocal quota file header of such an image claims zero chunks, the firstquota entry allocated during the mount gets a chunk number taken from akernel pointer, and releasing that entry clears a bit far outside thechunk bitmap.\nThe write will corrupt the data stored at that address, and thecorruption may lead to a system crash or damage unrelated data. Mounting requires CAP_SYS_ADMIN, so it takes an untrusted image, suchas removable media or a loop mount of a file from elsewhere.\nSince the chunk number comes from a kernel pointer, the address of thebit that gets cleared differs from boot to boot, and the issue has beenreported under several titles:\n- BUG: unable to handle kernel paging request in ocfs2_local_release_dquot- KASAN: use-after-free Write in ocfs2_local_release_dquot- KASAN: slab-out-of-bounds Write in ocfs2_local_release_dquot- KASAN: slab-use-after-free Write in ocfs2_local_release_dquot- KFENCE: use-after-free write in ocfs2_local_release_dquot\nNote that none of these is a use-after-free in the quota code: thechunk and its buffer head are alive.  The bit that gets cleared liesfar outside the bitmap.  KASAN and KFENCE name each report based on theobject occupying that address, which explains why the same issue isreported under so many different titles.  In the report I sent, theaddress fell in a free page, which KASAN labels use-after-free.\nThere are known reproducers.  Both a syzkaller and a C reproducer areavailable from the Google Drive link [1] in my report thread.  Theissue was found by our modified syzkaller, not a theoretical thingfound by an LLM.  I have not seen it outside fuzzing, so it is notaffecting me in the real world.\nThe local quota file in OCFS2 is divided into chunks, and each chunkbegins with a header block holding a bitmap of the quota entries thatchunk has handed out.  Chunks are numbered from zero, and that number isused to convert the file offset of an entry back into a bit position inthe bitmap.  ocfs2_local_quota_add_chunk() appends a new chunk to thein-memory list and numbers it one past the chunk that was last:\n\tlist_add_tail(&amp;chunk-&gt;qc_chunk, &amp;oinfo-&gt;dqi_chunk);\tchunk-&gt;qc_num = list_entry(chunk-&gt;qc_chunk.prev,\t\t\t\t   struct ocfs2_quota_chunk,\t\t\t\t   qc_chunk)-&gt;qc_num + 1;\nThe predecessor is looked up after the new chunk is added to the list, soif the list was empty, the prev pointer is the list head itself.  The headis the dqi_chunk member of struct ocfs2_mem_dqinfo and is not a chunk, soreading qc_num through it lands 16 bytes past the start of the head, onthe dqi_gqinode pointer that follows it.  The first chunk of the file isthen numbered with the lower half of a kernel pointer instead of 0.\nThe list is empty when the local quota file header claims the file has nochunks.  ocfs2_local_read_info() takes dqi_chunks from that header withoutvalidating it, so an image with dqi_chunks == 0 takes this path when thefirst quota entry is allocated.\nocfs2_create_local_dquot() turns the bad number into a file offset withol_dqblk_off(), which shifts a 32-bit block number left by the block sizebits, so the top bits of such a large block number are lost. ocfs2_local_release_dquot() turns the offset back into a bit index withol_dqblk_chunk_off(), using the full chunk number, so the lost bits pushthat index far outside the bitmap, and clearing it corrupts unrelatedmemory.\nCompute the chunk number before putting the chunk on the list, and use 0when the list is empty.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99430https://git.kernel.org/stable/c/76986d0ad2e1b71a304db59980f7d3440709cf69https://git.kernel.org/stable/c/59d336153d40649afe86ff57d3bde1ac1588e850https://git.kernel.org/stable/c/5778be09eab716b7d37f653d72c2c34a25f6ba05https://git.kernel.org/stable/c/4effccfd50baee4f325694964aeee997dca7bd96#kernel #Linux#CVE_2026_99430#bot", "url": "https://infosec.exchange/users/cve/statuses/117643964547882294"}, {"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-99430", "record": "DEBIAN-CVE-2026-99430", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T09:23:02.285Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:41:03.138Z", "date_only": false, "value": "2026-11-19T14:41:03.138Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99430", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:41:03.138Z", "date_only": false, "value": "2026-11-19T14:41:03.138Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99430", "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": 67319.14784, "hours": 18.69976328888889, "days": 0.7791568037037038, "min_seconds": 67319.14784, "max_seconds": 67319.14784, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:41:03.138Z", "date_only": false, "value": "2026-11-19T14:41:03.138Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99430", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T09:23:02.285Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
