{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.3-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  fbdev: omap2: fix use-after-free in omapfb_mmap  omapfb_mmap() has a race condition with OMAPFB_SETUP_PLANE ioctl that can lead to use-after-free:  The fb_mmap() entry point holds mm_lock but not lock (fb_info-\u003elock), while ioctl handlers like OMAPFB_SETUP_PLANE hold lock but not mm_lock. This allows concurrent execution.  In omapfb_mmap(): 1. rg = omapfb_get_mem_region(ofbi-\u003eregion);      // Get old region ref 2. start = omapfb_get_region_paddr(ofbi);          // Read from NEW region 3. len = fix-\u003esmem_len;                             // Read from NEW region 4. vm_iomap_memory(vma, start, len);               // Map NEW region memory 5. atomic_inc(\u0026rg-\u003emap_count);                      // Increment OLD region!  Concurrently, OMAPFB_SETUP_PLANE can: - Reassign ofbi-\u003eregion = new_rg - Update fix-\u003esmem_len - OMAPFB_SETUP_MEM then checks NEW region's map_count (0!) and frees it  This leaves userspace with a mapping to freed physical memory.  The fix is to read all required values (start, len) from the same region reference (rg) that will have its map_count incremented, preventing the region from being freed while still mapped.",
  "id": "DEBIAN-CVE-2026-53401",
  "modified": "2026-09-14T16:47:47.825462762Z",
  "published": "2026-07-19T12:16:51.287Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-53401"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-53401"
  ]
}