{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  bpf: Fix mmap_lock deadlock on arena lock failure  Reported by the Sashiko AI review.  arena_vm_fault() returns VM_FAULT_RETRY when it can't take arena-\u003espinlock, but it never took mmap_lock. The fault path assumes a VM_FAULT_RETRY handler already dropped mmap_lock and re-takes it on the retry, so mmap_lock gets taken twice and can deadlock:  \tdo_user_addr_fault() \t{ \t\tfault = handle_mm_fault(...);   // calls arena_vm_fault() \t\tif (fault \u0026 VM_FAULT_RETRY) \t\t\tgoto retry;   // re-locks mmap_lock \t\tmmap_read_unlock(mm); \t}  Return VM_FAULT_SIGBUS instead, for two reasons:  1. We could keep VM_FAULT_RETRY, but then we'd have to drop the fault    lock first and cap the retry ourselves, the way __folio_lock_or_retry()    does.  2. A failed raw_res_spin_lock_irqsave() already means a possible deadlock    was detected, so retrying just hits the same lock again.  So returning VM_FAULT_RETRY here is overkill.",
  "id": "DEBIAN-CVE-2026-90342",
  "modified": "2026-09-18T04:47:38.053133288Z",
  "published": "2026-09-17T17:17:32.877Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-90342"
    }
  ],
  "upstream": [
    "CVE-2026-90342"
  ]
}