{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.176-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.85-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.14-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix out-of-bounds write in ocfs2_write_end_inline  KASAN reports a use-after-free write of 4086 bytes in ocfs2_write_end_inline, called from ocfs2_write_end_nolock during a copy_file_range splice fallback on a corrupted ocfs2 filesystem mounted on a loop device.  The actual bug is an out-of-bounds write past the inode block buffer, not a true use-after-free.  The write overflows into an adjacent freed page, which KASAN reports as UAF.  The root cause is that ocfs2_try_to_write_inline_data trusts the on-disk id_count field to determine whether a write fits in inline data.  On a corrupted filesystem, id_count can exceed the physical maximum inline data capacity, causing writes to overflow the inode block buffer.  Call trace (crash path):     vfs_copy_file_range (fs/read_write.c:1634)      do_splice_direct        splice_direct_to_actor          iter_file_splice_write            ocfs2_file_write_iter              generic_perform_write                ocfs2_write_end                  ocfs2_write_end_nolock (fs/ocfs2/aops.c:1949)                    ocfs2_write_end_inline (fs/ocfs2/aops.c:1915)                      memcpy_from_folio     \u003c-- KASAN: write OOB  So add id_count upper bound check in ocfs2_validate_inode_block() to alongside the existing i_size check to fix it.",
  "id": "DEBIAN-CVE-2026-43075",
  "modified": "2026-09-14T16:47:27.983746730Z",
  "published": "2026-05-06T10:16:20.463Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-43075"
    }
  ],
  "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-43075"
  ]
}