CVE-2026-43285

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

mm/slab: do not access current->mems_allowed_seq if !allow_spin

Lockdep complains when get_from_any_partial() is called in an NMI

context, because current->mems_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} -> {IN-NMI} usage.

kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes:

ffff889085799820 (&____s->seqcount#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): [<ffffffff850a68d7>] _raw_spin_unlock_irq+0x27/0x70

hardirqs last disabled at (56): [<ffffffff850858ca>] __sched

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References