{
  "affected": [
    {
      "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"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  ring-buffer: Fix the sub-buffer array base in rb_meta_subbuf_idx()  On a persistent ring buffer, rb_meta_subbuf_idx() can return an index one sub-buffer too high.  rb_setup_ids_meta_page() then fills subbuf_ids[] shifted by one and leaves subbuf_ids[0] NULL, which __rb_map_vma() dereferences when userspace maps trace_pipe_raw.  rb_update_meta_reader() writes two such indices into meta-\u003ebuffers[], which rb_cpu_meta_valid() would reject on the next boot, discarding the previous boot's trace.  A CPU's sub-buffer array starts after its meta header and the nr_subbufs integers that follow, aligned up to a sub-buffer.  rb_meta_subbuf_idx() inverts that calculation but skips only the integers, not the header, so its base is one sub-buffer low whenever the omitted header size crosses the alignment boundary.  Invert the calculation with rb_subbufs_from_meta() rather than repeating it.  rb_range_buffer() maps an index back to an address through the same helper, so the two directions can no longer disagree.",
  "id": "DEBIAN-CVE-2026-99159",
  "modified": "2026-10-29T05:47:24.463376174Z",
  "published": "2026-10-28T11:17:36.160Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-99159"
    }
  ],
  "upstream": [
    "CVE-2026-99159"
  ]
}