{"api_version":"1","generated_at":"2026-10-04T11:44:17+00:00","cve":"CVE-2026-90342","urls":{"html":"https://cve.report/CVE-2026-90342","api":"https://cve.report/api/cve/CVE-2026-90342.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-90342","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90342"},"summary":{"title":"bpf: Fix mmap_lock deadlock on arena lock failure","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix mmap_lock deadlock on arena lock failure\n\nReported by the Sashiko AI review.\n\narena_vm_fault() returns VM_FAULT_RETRY when it can't take\narena->spinlock, but it never took mmap_lock. The fault path assumes a\nVM_FAULT_RETRY handler already dropped mmap_lock and re-takes it on the\nretry, so mmap_lock gets taken twice and can deadlock:\n\n\tdo_user_addr_fault()\n\t{\n\t\tfault = handle_mm_fault(...);   // calls arena_vm_fault()\n\t\tif (fault & VM_FAULT_RETRY)\n\t\t\tgoto retry;   // re-locks mmap_lock\n\t\tmmap_read_unlock(mm);\n\t}\n\nReturn VM_FAULT_SIGBUS instead, for two reasons:\n\n1. We could keep VM_FAULT_RETRY, but then we'd have to drop the fault\n   lock first and cap the retry ourselves, the way __folio_lock_or_retry()\n   does.\n\n2. A failed raw_res_spin_lock_irqsave() already means a possible deadlock\n   was detected, so retrying just hits the same lock again.\n\nSo returning VM_FAULT_RETRY here is overkill.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:32","updated_at":"2026-09-17 17:17:32"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/af8087f16714f7620c4db3e732baaa1b2337948f","name":"https://git.kernel.org/stable/c/af8087f16714f7620c4db3e732baaa1b2337948f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0b10b945479c954393d62ee3229d2f224a4ca91c","name":"https://git.kernel.org/stable/c/0b10b945479c954393d62ee3229d2f224a4ca91c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90342","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90342","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b8467290edab4bafae352bf3f317055669a1a458 af8087f16714f7620c4db3e732baaa1b2337948f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b8467290edab4bafae352bf3f317055669a1a458 0b10b945479c954393d62ee3229d2f224a4ca91c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * 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/arena.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"af8087f16714f7620c4db3e732baaa1b2337948f","status":"affected","version":"b8467290edab4bafae352bf3f317055669a1a458","versionType":"git"},{"lessThan":"0b10b945479c954393d62ee3229d2f224a4ca91c","status":"affected","version":"b8467290edab4bafae352bf3f317055669a1a458","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/bpf/arena.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.0"},{"lessThan":"7.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix mmap_lock deadlock on arena lock failure\n\nReported by the Sashiko AI review.\n\narena_vm_fault() returns VM_FAULT_RETRY when it can't take\narena->spinlock, but it never took mmap_lock. The fault path assumes a\nVM_FAULT_RETRY handler already dropped mmap_lock and re-takes it on the\nretry, so mmap_lock gets taken twice and can deadlock:\n\n\tdo_user_addr_fault()\n\t{\n\t\tfault = handle_mm_fault(...);   // calls arena_vm_fault()\n\t\tif (fault & VM_FAULT_RETRY)\n\t\t\tgoto retry;   // re-locks mmap_lock\n\t\tmmap_read_unlock(mm);\n\t}\n\nReturn VM_FAULT_SIGBUS instead, for two reasons:\n\n1. We could keep VM_FAULT_RETRY, but then we'd have to drop the fault\n   lock first and cap the retry ourselves, the way __folio_lock_or_retry()\n   does.\n\n2. A failed raw_res_spin_lock_irqsave() already means a possible deadlock\n   was detected, so retrying just hits the same lock again.\n\nSo returning VM_FAULT_RETRY here is overkill."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:08:53.010Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/af8087f16714f7620c4db3e732baaa1b2337948f"},{"url":"https://git.kernel.org/stable/c/0b10b945479c954393d62ee3229d2f224a4ca91c"}],"title":"bpf: Fix mmap_lock deadlock on arena lock failure","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-90342","datePublished":"2026-09-17T16:08:53.010Z","dateReserved":"2026-09-11T19:38:34.804Z","dateUpdated":"2026-09-17T16:08:53.010Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:32","lastModifiedDate":"2026-09-17 17:17:32","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"90342","Ordinal":"1","Title":"bpf: Fix mmap_lock deadlock on arena lock failure","CVE":"CVE-2026-90342","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"90342","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix mmap_lock deadlock on arena lock failure\n\nReported by the Sashiko AI review.\n\narena_vm_fault() returns VM_FAULT_RETRY when it can't take\narena->spinlock, but it never took mmap_lock. The fault path assumes a\nVM_FAULT_RETRY handler already dropped mmap_lock and re-takes it on the\nretry, so mmap_lock gets taken twice and can deadlock:\n\n\tdo_user_addr_fault()\n\t{\n\t\tfault = handle_mm_fault(...);   // calls arena_vm_fault()\n\t\tif (fault & VM_FAULT_RETRY)\n\t\t\tgoto retry;   // re-locks mmap_lock\n\t\tmmap_read_unlock(mm);\n\t}\n\nReturn VM_FAULT_SIGBUS instead, for two reasons:\n\n1. We could keep VM_FAULT_RETRY, but then we'd have to drop the fault\n   lock first and cap the retry ourselves, the way __folio_lock_or_retry()\n   does.\n\n2. A failed raw_res_spin_lock_irqsave() already means a possible deadlock\n   was detected, so retrying just hits the same lock again.\n\nSo returning VM_FAULT_RETRY here is overkill.","Type":"Description","Title":"bpf: Fix mmap_lock deadlock on arena lock failure"}]}}}