{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-53683",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-53683"
  ],
  "published": "2025-10-07T15:23:56Z",
  "summary": "fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode()\n\nsyzbot is hitting WARN_ON() in hfsplus_cat_{read,write}_inode(), for\ncrafted filesystem image can contain bogus length. There conditions are\nnot kernel bugs that can justify kernel to panic.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.21-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v6",
            "binary_version": "1:6.1.21-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v7",
            "binary_version": "1:6.1.21-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v7l",
            "binary_version": "1:6.1.21-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v8",
            "binary_version": "1:6.1.21-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.21-1+rpt1": {
            "linux_commit": "0afb5e98488aed7017b9bf321b575d0177feb7ed",
            "upstream_version": "6.1.21",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.30"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-53683"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/61af77acd039ffd221bf7adf0dc95d0a4d377505"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c074913b12db3632b11588b31bbfb0fa80a0a1c9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a75d9211a07fed513c08c5d4861c4a36ac6a74fe"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c8daee66585897a4c90d937c91e762100237bff9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/37cab61a52d6f42b2d961c51bcf369f09e235fb5"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/48960a503fcec76d3f72347b7e679dda08ca43be"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3a9d68d84b2e41ba3f2a727b36f035fad6800492"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/81b21c0f0138ff5a499eafc3eb0578ad2a99622c"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:24:39Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - Exploitation requires the crafted HFS+ image to be attached locally as a block/loop device and mounted, with the corrupt catalog record parsed by the local kernel. There is no network-facing path into the hfsplus catalog btree code.\nAC:L - The attacker fully authors the on-disk image, so `fd->entrylength` and `fd->entryoffset` are deterministic attacker-chosen u16 values from the record-offset table; no race, timing window, or uncontrollable memory layout is needed to reach the failed sanity check and the subsequent unbounded `hfs_bnode_read()`/`hfs_bnode_write()`.\nPR:L - Only ordinary local user access is required in the realistic scenario: an unprivileged logged-in user inserts an HFS+-formatted USB stick or SD card that udisks2/systemd automounts, and post-mount `hfsplus_cat_write_inode()` fires from normal writeback with no further privilege. This matches the scoring of the sibling fix CVE-2023-54130.\nUI:N - The attacker performs the mount themselves (or triggers automount by inserting their own media) and the write path is then reached automatically via inode writeback; no separate victim action is required.\nS:U - The out-of-bounds access and resulting corruption stay within the kernel's own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - Continuing past the failed length check makes `hfs_bnode_read()` index past `node->page[]` and dereference an adjacent-heap value as a `struct page *`, copying arbitrary kernel memory into the catalog entry, which is then exposed to userspace through `i_size`, uid/gid/mode, and `init_special_inode()` rdev.\nI:H - `hfsplus_cat_write_inode()` performs `hfs_bnode_write()` of a full 88/248-byte record at the unvalidated offset, giving an out-of-bounds kernel write (plus `set_page_dirty()` on a bogus pointer) with partially attacker-influenced contents \u2014 a corruption primitive usable for control-flow hijack, and at minimum silent metadata corruption.\nA:H - The `WARN_ON()` itself panics the kernel on `panic_on_warn=1` systems, and the wild `struct page *` dereference that follows reliably oopses or panics the kernel."
    }
  }
}