{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.6-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  mm/slab: do not access current-\u003emems_allowed_seq if !allow_spin  Lockdep complains when get_from_any_partial() is called in an NMI context, because current-\u003emems_allowed_seq is seqcount_spinlock_t and not NMI-safe:    ================================   WARNING: inconsistent lock state   6.19.0-rc5-kfree-rcu+ #315 Tainted: G                 N   --------------------------------   inconsistent {INITIAL USE} -\u003e {IN-NMI} usage.   kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes:   ffff889085799820 (\u0026____s-\u003eseqcount#3){.-.-}-{0:0}, at: ___slab_alloc+0x58f/0xc00   {INITIAL USE} state was registered at:     lock_acquire+0x185/0x320     kernel_init_freeable+0x391/0x1150     kernel_init+0x1f/0x220     ret_from_fork+0x736/0x8f0     ret_from_fork_asm+0x1a/0x30   irq event stamp: 56   hardirqs last  enabled at (55): [\u003cffffffff850a68d7\u003e] _raw_spin_unlock_irq+0x27/0x70   hardirqs last disabled at (56): [\u003cffffffff850858ca\u003e] __schedule+0x2a8a/0x6630   softirqs last  enabled at (0): [\u003cffffffff81536711\u003e] copy_process+0x1dc1/0x6a10   softirqs last disabled at (0): [\u003c0000000000000000\u003e] 0x0    other info that might help us debug this:    Possible unsafe locking scenario:           CPU0          ----     lock(\u0026____s-\u003eseqcount#3);     \u003cInterrupt\u003e       lock(\u0026____s-\u003eseqcount#3);     *** DEADLOCK ***  According to Documentation/locking/seqlock.rst, seqcount_t is not NMI-safe and seqcount_latch_t should be used when read path can interrupt the write-side critical section. In this case, do not access current-\u003emems_allowed_seq and avoid retry.",
  "id": "DEBIAN-CVE-2026-43285",
  "modified": "2026-09-14T16:47:29.798379001Z",
  "published": "2026-05-08T14:16:35.337Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-43285"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-43285"
  ]
}