Vulnerability-Lookup

GHSA-V2VH-P96V-7CC2

Vulnerability from github – Published: 2026-05-08 15:31 – Updated: 2026-05-08 15:31

Details

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): [] _raw_spin_unlock_irq+0x27/0x70 hardirqs last disabled at (56): [] __schedule+0x2a8a/0x6630 softirqs last enabled at (0): [] copy_process+0x1dc1/0x6a10 softirqs last disabled at (0): [<0000000000000000>] 0x0

other info that might help us debug this: Possible unsafe locking scenario:

     CPU0
     ----
lock(&____s->seqcount#3);
<Interrupt>
  lock(&____s->seqcount#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->mems_allowed_seq and avoid retry.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-43285"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-08T14:16:35Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/slab: do not access current-\u003emems_allowed_seq if !allow_spin\n\nLockdep complains when get_from_any_partial() is called in an NMI\ncontext, because current-\u003emems_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} -\u003e {IN-NMI} usage.\n  kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes:\n  ffff889085799820 (\u0026____s-\u003eseqcount#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): [\u003cffffffff850a68d7\u003e] _raw_spin_unlock_irq+0x27/0x70\n  hardirqs last disabled at (56): [\u003cffffffff850858ca\u003e] __schedule+0x2a8a/0x6630\n  softirqs last  enabled at (0): [\u003cffffffff81536711\u003e] copy_process+0x1dc1/0x6a10\n  softirqs last disabled at (0): [\u003c0000000000000000\u003e] 0x0\n\n  other info that might help us debug this:\n   Possible unsafe locking scenario:\n\n         CPU0\n         ----\n    lock(\u0026____s-\u003eseqcount#3);\n    \u003cInterrupt\u003e\n      lock(\u0026____s-\u003eseqcount#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-\u003emems_allowed_seq and avoid retry.",
  "id": "GHSA-v2vh-p96v-7cc2",
  "modified": "2026-05-08T15:31:22Z",
  "published": "2026-05-08T15:31:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-43285"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/144080a5823b2dbd635acb6decf7ab23182664f3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/353dd9934447b9193643ae1afd938607a74d4915"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/efd767ddcef0669bbd33c6a823ea0a88f06d4b29"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-43285 (GCVE-0-2026-43285)

Vulnerability from cvelistv5 – Published: 2026-05-08 13:11 – Updated: 2026-05-08 13:11

Title

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

Summary

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>] __schedule+0x2a8a/0x6630 softirqs last enabled at (0): [<ffffffff81536711>] copy_process+0x1dc1/0x6a10 softirqs last disabled at (0): [<0000000000000000>] 0x0 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&____s->seqcount#3); <Interrupt> lock(&____s->seqcount#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->mems_allowed_seq and avoid retry.

Severity ?

No CVSS data available.

Assigner

Linux

References

URL

Tags

	https://git.kernel.org/stable/c/353dd9934447b9193…
	https://git.kernel.org/stable/c/efd767ddcef0669bb…
	https://git.kernel.org/stable/c/144080a5823b2dbd6…

Impacted products

Vendor

Product

Version

Linux

Affected: af92793e52c3a99b828ed4bdd277fd3e11c18d08 , < 353dd9934447b9193643ae1afd938607a74d4915 (git)
Affected: af92793e52c3a99b828ed4bdd277fd3e11c18d08 , < efd767ddcef0669bbd33c6a823ea0a88f06d4b29 (git)
Affected: af92793e52c3a99b828ed4bdd277fd3e11c18d08 , < 144080a5823b2dbd635acb6decf7ab23182664f3 (git)

Linux

Affected: 6.18
Unaffected: 0 , < 6.18 (semver)
Unaffected: 6.18.16 , ≤ 6.18.* (semver)
Unaffected: 6.19.6 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "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-\u003emems_allowed_seq if !allow_spin\n\nLockdep complains when get_from_any_partial() is called in an NMI\ncontext, because current-\u003emems_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} -\u003e {IN-NMI} usage.\n  kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes:\n  ffff889085799820 (\u0026____s-\u003eseqcount#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): [\u003cffffffff850a68d7\u003e] _raw_spin_unlock_irq+0x27/0x70\n  hardirqs last disabled at (56): [\u003cffffffff850858ca\u003e] __schedule+0x2a8a/0x6630\n  softirqs last  enabled at (0): [\u003cffffffff81536711\u003e] copy_process+0x1dc1/0x6a10\n  softirqs last disabled at (0): [\u003c0000000000000000\u003e] 0x0\n\n  other info that might help us debug this:\n   Possible unsafe locking scenario:\n\n         CPU0\n         ----\n    lock(\u0026____s-\u003eseqcount#3);\n    \u003cInterrupt\u003e\n      lock(\u0026____s-\u003eseqcount#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-\u003emems_allowed_seq and avoid retry."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-08T13:11:11.191Z",
        "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-\u003emems_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-08T13:11:11.191Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

GHSA-V2VH-P96V-7CC2

CVE-2026-43285 (GCVE-0-2026-43285)

Tags

Sightings

Nomenclature