{
  "cveId": "CVE-2023-52449",
  "url": "https://patchblox.com/security/cve/CVE-2023-52449",
  "summary": "CVE-2023-52449 is fixed in linux on 1 platform, first by DEBIAN-CVE-2023-52449, released February 22, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  mtd: Fix gluebi NULL pointer dereference caused...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: Fix gluebi NULL pointer dereference caused by ftl notifier  If both ftl.ko and gluebi.ko are loaded, the notifier of ftl triggers NULL pointer dereference when trying to access \u2018gluebi-\u003Edesc\u2019 in gluebi_read().  ubi_gluebi_init   ubi_register_volume_notifier     ubi_enumerate_volumes       ubi_notify_all         gluebi_notify    nb-\u003Enotifier_call()           gluebi_create             mtd_device_register               mtd_device_parse_register                 add_mtd_device                   blktrans_notify_add   not-\u003Eadd()                     ftl_add_mtd         tr-\u003Eadd_mtd()                       scan_header                         mtd_read                           mtd_read_oob                             mtd_read_oob_std                               gluebi_read   mtd-\u003Eread()                                 gluebi-\u003Edesc - NULL  Detailed reproduction information available at the Link [1],  In the normal case, obtain gluebi-\u003Edesc in the gluebi_get_device(), and access gluebi-\u003Edesc in the gluebi_read(). However, gluebi_get_device() is not executed in advance in the ftl_add_mtd() process, which leads to NULL pointer dereference.  The solution for the gluebi module is to run jffs2 on the UBI volume without considering working with ftl or mtdblock [2]. Therefore, this problem can be avoided by preventing gluebi from creating the mtdblock device after creating mtd partition of the type MTD_UBIVOLUME.",
  "published": "2024-02-22T17:15:08Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00242,
  "epssPercentile": 0.15453,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.76-1",
      "fix": "DEBIAN-CVE-2023-52449",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-52449",
      "released": "2024-02-22T17:15:08Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.6.15-1",
      "fix": "DEBIAN-CVE-2023-52449",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-52449",
      "released": "2024-02-22T17:15:08Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.6.15-1",
      "fix": "DEBIAN-CVE-2023-52449",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-52449",
      "released": "2024-02-22T17:15:08Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T01:18:40Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}