xfrm: retry inexact policy lookup after node reinsertion
Summary
| CVE | CVE-2026-99786 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:18:17 UTC |
| Updated | 2026-11-20 06:18:17 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
xfrm: retry inexact policy lookup after node reinsertion
An inexact policy lookup first records pointers to candidate hlist heads
and then traverses the lists. A concurrent policy insertion can merge
inexact tree nodes between those operations:
lookup policy insertion
------ ----------------
find inexact candidates
save obsolete hlist head
write_seqcount_begin(&bin->count)
merge inexact tree nodes
hlist_del_rcu(&policy->bydst)
reinsert policy->bydst in survivor
write_seqcount_end(&bin->count)
evaluate saved candidate list
miss the moved policy
The merge immediately reinserts the same hlist node into the surviving
tree node. RCU keeps the policy alive, but it does not provide a
consistent view while its list node is moved. A lookup that selected the
obsolete list can observe it empty. A lookup already traversing a moved
policy can instead follow the next pointer rewritten by the reinsertion.
Either case can return an incorrect IPsec policy result.
The per-bin sequence counter already brackets calls to
xfrm_policy_inexact_insert_node(), including node merges. The read side,
however, currently validates the counter only while searching an
individual rb-tree. A successful search returns without validation, and
the later candidate-list traversal is outside that read-side section.
Snapshot the per-bin sequence before discovering candidate heads and
validate it after evaluating all candidate lists. Retry the lookup if
the inexact policy tree changes while it is being searched. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 9cf545ebd591da673bb6b6c88150212ad83567a9 f10bd6c317cef7aa15e185e514513e8548f9ce77 git |
Not specified |
| CNA |
Linux |
Linux |
affected 9cf545ebd591da673bb6b6c88150212ad83567a9 6f66839895b7e9c2673df5bd9dd8d5a82033c825 git |
Not specified |
| CNA |
Linux |
Linux |
affected 9cf545ebd591da673bb6b6c88150212ad83567a9 50d8f2c52093320c70676e9f8af686ff6740abd0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 9cf545ebd591da673bb6b6c88150212ad83567a9 868f63c8bfafa9b827168c9126f85264c39c02ec git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.0 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.0 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.118 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.64 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3.5 7.3.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.4-rc2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/868f63c8bfafa9b827168c9126f85264c39c02ec |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/f10bd6c317cef7aa15e185e514513e8548f9ce77 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6f66839895b7e9c2673df5bd9dd8d5a82033c825 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/50d8f2c52093320c70676e9f8af686ff6740abd0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.