{"api_version":"1","generated_at":"2026-09-25T12:40:15+00:00","cve":"CVE-2026-98060","urls":{"html":"https://cve.report/CVE-2026-98060","api":"https://cve.report/api/cve/CVE-2026-98060.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98060","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98060"},"summary":{"title":"bpf: Reject resilient lock operations in rbtree callbacks","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject resilient lock operations in rbtree callbacks\n\n__bpf_rbtree_add() keeps parent and link pointers live across calls to the\nprogram-supplied comparison callback. The verifier therefore requires the\nroot's lock to remain held throughout the callback.\n\nThe helper path enforces this rule for bpf_spin_lock() and\nbpf_spin_unlock(), but the resilient lock kfunc argument path does not.\nSince resilient locks may protect BPF rbtree roots, a callback can release\nthe root lock and let another CPU remove and free the node referenced by\nthe in-progress tree walk. The walk then resumes using freed pointers.\n\nReject resilient lock kfuncs in an rbtree comparison callback, matching\nthe existing policy for the spin lock helpers. Resilient-lock-protected\ntrees remain valid when their comparison callbacks leave lock state alone.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:35","updated_at":"2026-09-25 11:17:35"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/71930202a0a0c49f0a3b45b41907a074cb780266","name":"https://git.kernel.org/stable/c/71930202a0a0c49f0a3b45b41907a074cb780266","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cc2e065ed206aecd9b94564779244f3ffb26e356","name":"https://git.kernel.org/stable/c/cc2e065ed206aecd9b94564779244f3ffb26e356","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7b7b8b5960102566bd625ae829d1f330c5b5d104","name":"https://git.kernel.org/stable/c/7b7b8b5960102566bd625ae829d1f330c5b5d104","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98060","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98060","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0de2046137f976e7302d43ac01d9894d07ac1fff cc2e065ed206aecd9b94564779244f3ffb26e356 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0de2046137f976e7302d43ac01d9894d07ac1fff 71930202a0a0c49f0a3b45b41907a074cb780266 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0de2046137f976e7302d43ac01d9894d07ac1fff 7b7b8b5960102566bd625ae829d1f330c5b5d104 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/bpf/verifier.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"cc2e065ed206aecd9b94564779244f3ffb26e356","status":"affected","version":"0de2046137f976e7302d43ac01d9894d07ac1fff","versionType":"git"},{"lessThan":"71930202a0a0c49f0a3b45b41907a074cb780266","status":"affected","version":"0de2046137f976e7302d43ac01d9894d07ac1fff","versionType":"git"},{"lessThan":"7b7b8b5960102566bd625ae829d1f330c5b5d104","status":"affected","version":"0de2046137f976e7302d43ac01d9894d07ac1fff","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/bpf/verifier.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.15"},{"lessThan":"6.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc2","versionStartIncluding":"6.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject resilient lock operations in rbtree callbacks\n\n__bpf_rbtree_add() keeps parent and link pointers live across calls to the\nprogram-supplied comparison callback. The verifier therefore requires the\nroot's lock to remain held throughout the callback.\n\nThe helper path enforces this rule for bpf_spin_lock() and\nbpf_spin_unlock(), but the resilient lock kfunc argument path does not.\nSince resilient locks may protect BPF rbtree roots, a callback can release\nthe root lock and let another CPU remove and free the node referenced by\nthe in-progress tree walk. The walk then resumes using freed pointers.\n\nReject resilient lock kfuncs in an rbtree comparison callback, matching\nthe existing policy for the spin lock helpers. Resilient-lock-protected\ntrees remain valid when their comparison callbacks leave lock state alone."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:24:05.380Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/cc2e065ed206aecd9b94564779244f3ffb26e356"},{"url":"https://git.kernel.org/stable/c/71930202a0a0c49f0a3b45b41907a074cb780266"},{"url":"https://git.kernel.org/stable/c/7b7b8b5960102566bd625ae829d1f330c5b5d104"}],"title":"bpf: Reject resilient lock operations in rbtree callbacks","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98060","datePublished":"2026-09-25T10:24:05.380Z","dateReserved":"2026-09-25T10:19:56.073Z","dateUpdated":"2026-09-25T10:24:05.380Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:35","lastModifiedDate":"2026-09-25 11:17:35","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98060","Ordinal":"1","Title":"bpf: Reject resilient lock operations in rbtree callbacks","CVE":"CVE-2026-98060","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98060","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject resilient lock operations in rbtree callbacks\n\n__bpf_rbtree_add() keeps parent and link pointers live across calls to the\nprogram-supplied comparison callback. The verifier therefore requires the\nroot's lock to remain held throughout the callback.\n\nThe helper path enforces this rule for bpf_spin_lock() and\nbpf_spin_unlock(), but the resilient lock kfunc argument path does not.\nSince resilient locks may protect BPF rbtree roots, a callback can release\nthe root lock and let another CPU remove and free the node referenced by\nthe in-progress tree walk. The walk then resumes using freed pointers.\n\nReject resilient lock kfuncs in an rbtree comparison callback, matching\nthe existing policy for the spin lock helpers. Resilient-lock-protected\ntrees remain valid when their comparison callbacks leave lock state alone.","Type":"Description","Title":"bpf: Reject resilient lock operations in rbtree callbacks"}]}}}