{"api_version":"1","generated_at":"2026-05-13T03:32:08+00:00","cve":"CVE-2026-43285","urls":{"html":"https://cve.report/CVE-2026-43285","api":"https://cve.report/api/cve/CVE-2026-43285.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-43285","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-43285"},"summary":{"title":"mm/slab: do not access current->mems_allowed_seq if !allow_spin","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/slab: do not access current->mems_allowed_seq if !allow_spin\n\nLockdep complains when get_from_any_partial() is called in an NMI\ncontext, because current->mems_allowed_seq is seqcount_spinlock_t and\nnot NMI-safe:\n\n  ================================\n  WARNING: inconsistent lock state\n  6.19.0-rc5-kfree-rcu+ #315 Tainted: G                 N\n  --------------------------------\n  inconsistent {INITIAL USE} -> {IN-NMI} usage.\n  kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes:\n  ffff889085799820 (&____s->seqcount#3){.-.-}-{0:0}, at: ___slab_alloc+0x58f/0xc00\n  {INITIAL USE} state was registered at:\n    lock_acquire+0x185/0x320\n    kernel_init_freeable+0x391/0x1150\n    kernel_init+0x1f/0x220\n    ret_from_fork+0x736/0x8f0\n    ret_from_fork_asm+0x1a/0x30\n  irq event stamp: 56\n  hardirqs last  enabled at (55): [<ffffffff850a68d7>] _raw_spin_unlock_irq+0x27/0x70\n  hardirqs last disabled at (56): [<ffffffff850858ca>] __schedule+0x2a8a/0x6630\n  softirqs last  enabled at (0): [<ffffffff81536711>] copy_process+0x1dc1/0x6a10\n  softirqs last disabled at (0): [<0000000000000000>] 0x0\n\n  other info that might help us debug this:\n   Possible unsafe locking scenario:\n\n         CPU0\n         ----\n    lock(&____s->seqcount#3);\n    <Interrupt>\n      lock(&____s->seqcount#3);\n\n   *** DEADLOCK ***\n\nAccording to Documentation/locking/seqlock.rst, seqcount_t is not\nNMI-safe and seqcount_latch_t should be used when read path can interrupt\nthe write-side critical section. In this case, do not access\ncurrent->mems_allowed_seq and avoid retry.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-08 14:16:35","updated_at":"2026-05-12 14:10:27"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/efd767ddcef0669bbd33c6a823ea0a88f06d4b29","name":"https://git.kernel.org/stable/c/efd767ddcef0669bbd33c6a823ea0a88f06d4b29","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/144080a5823b2dbd635acb6decf7ab23182664f3","name":"https://git.kernel.org/stable/c/144080a5823b2dbd635acb6decf7ab23182664f3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/353dd9934447b9193643ae1afd938607a74d4915","name":"https://git.kernel.org/stable/c/353dd9934447b9193643ae1afd938607a74d4915","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-43285","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43285","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected af92793e52c3a99b828ed4bdd277fd3e11c18d08 353dd9934447b9193643ae1afd938607a74d4915 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected af92793e52c3a99b828ed4bdd277fd3e11c18d08 efd767ddcef0669bbd33c6a823ea0a88f06d4b29 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected af92793e52c3a99b828ed4bdd277fd3e11c18d08 144080a5823b2dbd635acb6decf7ab23182664f3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.16 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19.6 6.19.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"43285","cve":"CVE-2026-43285","epss":"0.000170000","percentile":"0.041320000","score_date":"2026-05-12","updated_at":"2026-05-13 00:11:53"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/slub.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"353dd9934447b9193643ae1afd938607a74d4915","status":"affected","version":"af92793e52c3a99b828ed4bdd277fd3e11c18d08","versionType":"git"},{"lessThan":"efd767ddcef0669bbd33c6a823ea0a88f06d4b29","status":"affected","version":"af92793e52c3a99b828ed4bdd277fd3e11c18d08","versionType":"git"},{"lessThan":"144080a5823b2dbd635acb6decf7ab23182664f3","status":"affected","version":"af92793e52c3a99b828ed4bdd277fd3e11c18d08","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/slub.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.18"},{"lessThan":"6.18","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.16","versionType":"semver"},{"lessThanOrEqual":"6.19.*","status":"unaffected","version":"6.19.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.0","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.16","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.19.6","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0","versionStartIncluding":"6.18","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/slab: do not access current->mems_allowed_seq if !allow_spin\n\nLockdep complains when get_from_any_partial() is called in an NMI\ncontext, because current->mems_allowed_seq is seqcount_spinlock_t and\nnot NMI-safe:\n\n  ================================\n  WARNING: inconsistent lock state\n  6.19.0-rc5-kfree-rcu+ #315 Tainted: G                 N\n  --------------------------------\n  inconsistent {INITIAL USE} -> {IN-NMI} usage.\n  kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes:\n  ffff889085799820 (&____s->seqcount#3){.-.-}-{0:0}, at: ___slab_alloc+0x58f/0xc00\n  {INITIAL USE} state was registered at:\n    lock_acquire+0x185/0x320\n    kernel_init_freeable+0x391/0x1150\n    kernel_init+0x1f/0x220\n    ret_from_fork+0x736/0x8f0\n    ret_from_fork_asm+0x1a/0x30\n  irq event stamp: 56\n  hardirqs last  enabled at (55): [<ffffffff850a68d7>] _raw_spin_unlock_irq+0x27/0x70\n  hardirqs last disabled at (56): [<ffffffff850858ca>] __schedule+0x2a8a/0x6630\n  softirqs last  enabled at (0): [<ffffffff81536711>] copy_process+0x1dc1/0x6a10\n  softirqs last disabled at (0): [<0000000000000000>] 0x0\n\n  other info that might help us debug this:\n   Possible unsafe locking scenario:\n\n         CPU0\n         ----\n    lock(&____s->seqcount#3);\n    <Interrupt>\n      lock(&____s->seqcount#3);\n\n   *** DEADLOCK ***\n\nAccording to Documentation/locking/seqlock.rst, seqcount_t is not\nNMI-safe and seqcount_latch_t should be used when read path can interrupt\nthe write-side critical section. In this case, do not access\ncurrent->mems_allowed_seq and avoid retry."}],"providerMetadata":{"dateUpdated":"2026-05-11T22:21:36.072Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/353dd9934447b9193643ae1afd938607a74d4915"},{"url":"https://git.kernel.org/stable/c/efd767ddcef0669bbd33c6a823ea0a88f06d4b29"},{"url":"https://git.kernel.org/stable/c/144080a5823b2dbd635acb6decf7ab23182664f3"}],"title":"mm/slab: do not access current->mems_allowed_seq if !allow_spin","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-43285","datePublished":"2026-05-08T13:11:11.191Z","dateReserved":"2026-05-01T14:12:55.999Z","dateUpdated":"2026-05-11T22:21:36.072Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-08 14:16:35","lastModifiedDate":"2026-05-12 14:10:27","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"43285","Ordinal":"1","Title":"mm/slab: do not access current->mems_allowed_seq if !allow_spin","CVE":"CVE-2026-43285","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"43285","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/slab: do not access current->mems_allowed_seq if !allow_spin\n\nLockdep complains when get_from_any_partial() is called in an NMI\ncontext, because current->mems_allowed_seq is seqcount_spinlock_t and\nnot NMI-safe:\n\n  ================================\n  WARNING: inconsistent lock state\n  6.19.0-rc5-kfree-rcu+ #315 Tainted: G                 N\n  --------------------------------\n  inconsistent {INITIAL USE} -> {IN-NMI} usage.\n  kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes:\n  ffff889085799820 (&____s->seqcount#3){.-.-}-{0:0}, at: ___slab_alloc+0x58f/0xc00\n  {INITIAL USE} state was registered at:\n    lock_acquire+0x185/0x320\n    kernel_init_freeable+0x391/0x1150\n    kernel_init+0x1f/0x220\n    ret_from_fork+0x736/0x8f0\n    ret_from_fork_asm+0x1a/0x30\n  irq event stamp: 56\n  hardirqs last  enabled at (55): [<ffffffff850a68d7>] _raw_spin_unlock_irq+0x27/0x70\n  hardirqs last disabled at (56): [<ffffffff850858ca>] __schedule+0x2a8a/0x6630\n  softirqs last  enabled at (0): [<ffffffff81536711>] copy_process+0x1dc1/0x6a10\n  softirqs last disabled at (0): [<0000000000000000>] 0x0\n\n  other info that might help us debug this:\n   Possible unsafe locking scenario:\n\n         CPU0\n         ----\n    lock(&____s->seqcount#3);\n    <Interrupt>\n      lock(&____s->seqcount#3);\n\n   *** DEADLOCK ***\n\nAccording to Documentation/locking/seqlock.rst, seqcount_t is not\nNMI-safe and seqcount_latch_t should be used when read path can interrupt\nthe write-side critical section. In this case, do not access\ncurrent->mems_allowed_seq and avoid retry.","Type":"Description","Title":"mm/slab: do not access current->mems_allowed_seq if !allow_spin"}]}}}