{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-90342","id":"CVE-2026-90342","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 c","descriptionLong":"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.","published":"2026-09-17T16:08:53.010Z","updated":"2026-10-28T02:30:45.032823366Z","reserved":"2026-09-11T19:38:34.804Z","status":"Received","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"b8467290edab4bafae352bf3f317055669a1a458","lessThan":"af8087f16714f7620c4db3e732baaa1b2337948f","status":"affected","versionType":"git"},{"version":"b8467290edab4bafae352bf3f317055669a1a458","lessThan":"0b10b945479c954393d62ee3229d2f224a4ca91c","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"7.0","status":"affected"},{"version":"0","lessThan":"7.0","status":"unaffected","versionType":"semver"},{"version":"7.2.6","lessThanOrEqual":"7.2.*","status":"unaffected","versionType":"semver"},{"version":"7.3","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/af8087f16714f7620c4db3e732baaa1b2337948f","tags":["web"]},{"url":"https://git.kernel.org/stable/c/0b10b945479c954393d62ee3229d2f224a4ca91c","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90342.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90342","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":0.00198,"epssPercentile":0.09576,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-90342","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90342","ok":true,"note":"Received"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-90342","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-90342","ok":true,"note":"scored 2026-11-18"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}