{"metadata": {"vulnerability": "CVE-2026-99429", "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-99429", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:40:51.812Z", "date_only": false, "value": "2026-11-19T14:40:51.812Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99429", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:40:51.812Z", "date_only": false, "value": "2026-11-19T14:40:51.812Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99429", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:40:51.812Z", "date_only": false, "value": "2026-11-19T14:40:51.812Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99429", "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-H5JV-8253-3CFR", "record": "GHSA-H5JV-8253-3CFR", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:17:56.087Z", "date_only": false, "value": "2026-11-19T15:17:56.087", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99429", "record": "FKIE_CVE-2026-99429", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:17:56.087Z", "date_only": false, "value": "2026-11-19T15:17:56.087", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99429", "record": "FKIE_CVE-2026-99429", "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-H5JV-8253-3CFR", "record": "GHSA-H5JV-8253-3CFR", "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-H5JV-8253-3CFR", "record": "GHSA-H5JV-8253-3CFR", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T16:06:39.721Z", "date_only": false, "value": "2026-11-19T16:06:39.721109Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117643961900890062", "record": "CVE-2026-99429", "field": "creation_timestamp", "uuid": "5112d5c2-01f7-4c14-8b45-da18ad41798f", "content": "CVE-2026-99429 ocfs2: pin refcount trees before dropping the lookup lock In the Linux kernel, the following vulnerability has been resolved:\nocfs2: pin refcount trees before dropping the lookup lock\nA refcount tree returned to ocfs2_lock_refcount_tree() must stay aliveuntil that caller releases its operation reference. However,ocfs2_get_refcount_tree() returns the cached pointer after droppingosb_lock, and the caller only takes its kref afterwards. The registryreference does not protect this gap from concurrent removal.\nThis can happen when another node frees a refcount root and reuses itsblock with a different generation while this mount retains the oldcached tree. Two local operations on different inodes sharing the newroot, such as data CoW and an external xattr update, can then look upthe same stale tree. Their inode locks are independent, and both theREFCOUNT DLM lock and rf_sem are acquired after the first operationreference.\nThe following ordering is possible, with no other operation references:\n  Data CoW                         Xattr update  --------                         ------------  Look up the old tree under    osb_lock, then drop osb_lock                                   Look up the same tree and take a kref                                   Acquire the tree locks and read the                                     new on-disk generation                                   Erase the old tree under osb_lock                                   Unlock and drop the operation kref                                   Drop the registry kref, freeing tree  Take a kref through the    freed tree pointer\nThe final kref_get() accesses freed rf_getcnt storage, and subsequentaccesses in ocfs2_lock_refcount_tree() also use the freed allocation.\nTake the operation reference in ocfs2_get_refcount_tree() beforereleasing osb_lock, including when an insertion loses to another lookup.Removal must acquire the same lock, so it cannot drop the registryreference before the lookup has pinned the tree. Keep the existingunlock and error path puts. The two callers that already hold therefcount tree lock keep their borrowed lookup behavior and do notacquire an extra reference.\nKASAN report as below:\n    BUG: KASAN: slab-use-after-free in ocfs2_lock_refcount_tree+0x94a/0x9b0    Read of size 4 at addr ffff888117212820 by task python3/497\n[Kernel and hardware identification omitted.]\n    Call Trace:     &lt;TASK&gt;     dump_stack_lvl+0x93/0xd0     print_report+0xce/0x630     ? ocfs2_lock_refcount_tree+0x94a/0x9b0     ? srso_alias_return_thunk+0x5/0xfbef5     ? __virt_addr_valid+0x20e/0x420     ? ocfs2_lock_refcount_tree+0x94a/0x9b0     kasan_report+0xe0/0x110     ? ocfs2_lock_refcount_tree+0x94a/0x9b0     ocfs2_lock_refcount_tree+0x94a/0x9b0     ? __pfx_ocfs2_lock_refcount_tree+0x10/0x10     ? srso_alias_return_thunk+0x5/0xfbef5     ? ocfs2_refcount_cow+0x3b6/0xd90     ? srso_alias_return_thunk+0x5/0xfbef5     ? __kmalloc_cache_noprof+0x28d/0x610     ? ocfs2_refcount_cow+0x3b6/0xd90     ocfs2_refcount_cow+0x410/0xd90     ? __pfx_ocfs2_refcount_cow+0x10/0x10     ? __pfx___might_resched+0x10/0x10     ? down_write+0x11a/0x1f0     ? __pfx_down_write+0x10/0x10     ? ocfs2_inode_unlock+0x1a9/0x260     ? __pfx_ocfs2_inode_unlock+0x10/0x10     ? ocfs2_file_write_iter+0x1413/0x1d30     ocfs2_file_write_iter+0x157b/0x1d30     ? __pfx_ocfs2_file_write_iter+0x10/0x10     ? lock_acquire+0x190/0x300     ? __x64_sys_pwrite64+0x1b7/0x220     ? __pfx___might_resched+0x10/0x10     ? srso_alias_return_thunk+0x5/0xfbef5     ? security_file_permission+0x26/0x80     ? srso_alias_return_thunk+0x5/0xfbef5     ? lock_is_held_type+0x8f/0x100     vfs_write+0x639/0x1010     ? __pfx_ocfs2_file_write_iter+0x10/0x10     ? lock_vma_under_rcu+0x154/0x4a0     ? __pfx_vfs_write+0x10/0x10     ? lock_release+0x121/0x290     ? srso_alias_return_thunk+0x5/0xfbef5     __x64_sys_pwrite64+0x1b7/0x220     ? __pfx___x64_sys_pwrite64+0x10/0x10     ? irqentry_exit+0xbe/0x820---truncated---\nhttps://www.cve.org/CVERecord?id=CVE-2026-99429https://git.kernel.org/stable/c/ce7b46556af15642a1e9f8d0c596022dd7cfb4a7https://git.kernel.org/stable/c/7ff4f020f7b03fddd529735f0b61ac0a8dd92c9ehttps://git.kernel.org/stable/c/2d9e864c234469dc7f56ea974f8269d251441e6ahttps://git.kernel.org/stable/c/8c714a074074af7ae59233c1fa6ef9d7aa710462#kernel #Linux#CVE_2026_99429#bot", "url": "https://infosec.exchange/users/cve/statuses/117643961900890062"}, {"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-99429", "record": "DEBIAN-CVE-2026-99429", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T05:55:15.129Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:40:51.812Z", "date_only": false, "value": "2026-11-19T14:40:51.812Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99429", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:40:51.812Z", "date_only": false, "value": "2026-11-19T14:40:51.812Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99429", "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": 54863.317914, "hours": 15.239810531666667, "days": 0.6349921054861111, "min_seconds": 54863.317914, "max_seconds": 54863.317914, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:40:51.812Z", "date_only": false, "value": "2026-11-19T14:40:51.812Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99429", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T05:55:15.129Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
