Vulnerability-Lookup

GHSA-C4VG-43J9-MH2M

Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32

Details

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

nvmet: fix return status of RMI log page on allocation failure

nvmet_execute_get_log_page_rmi() leaves 'status' holding NVME_SC_SUCCESS (set by the successful nvmet_req_find_ns() call) when the kzalloc() for the log buffer fails. It then jumps to the out label and completes the request with a success status, so the host is told the command succeeded while no data was transferred.

Initialize 'status' to NVME_SC_INTERNAL, matching the smart log handler, so an allocation failure is reported as an internal error.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-90412"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-17T17:17:43Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix return status of RMI log page on allocation failure\n\nnvmet_execute_get_log_page_rmi() leaves \u0027status\u0027 holding NVME_SC_SUCCESS\n(set by the successful nvmet_req_find_ns() call) when the kzalloc() for\nthe log buffer fails. It then jumps to the out label and completes the\nrequest with a success status, so the host is told the command succeeded\nwhile no data was transferred.\n\nInitialize \u0027status\u0027 to NVME_SC_INTERNAL, matching the smart log handler,\nso an allocation failure is reported as an internal error.",
  "id": "GHSA-c4vg-43j9-mh2m",
  "modified": "2026-09-17T18:32:04Z",
  "published": "2026-09-17T18:32:04Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90412"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/581d8bb556dd3e5567bcf322aa5e3e4b6a200c08"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9e136150ac55df4b7ea36e6110ffa39d08905f37"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-90412 (GCVE-0-2026-90412)

Vulnerability from cvelistv5 – Published: 2026-09-17 16:09 – Updated: 2026-09-17 16:09

Title

nvmet: fix return status of RMI log page on allocation failure

Summary

In the Linux kernel, the following vulnerability has been resolved: nvmet: fix return status of RMI log page on allocation failure nvmet_execute_get_log_page_rmi() leaves 'status' holding NVME_SC_SUCCESS (set by the successful nvmet_req_find_ns() call) when the kzalloc() for the log buffer fails. It then jumps to the out label and completes the request with a success status, so the host is told the command succeeded while no data was transferred. Initialize 'status' to NVME_SC_INTERNAL, matching the smart log handler, so an allocation failure is reported as an internal error.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/9e136150ac55df4b7…
https://git.kernel.org/stable/c/581d8bb556dd3e556…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 5fd075cdaf3649000677d960fd9e45c08081b7e0 , < 9e136150ac55df4b7ea36e6110ffa39d08905f37 (git) Affected: 5fd075cdaf3649000677d960fd9e45c08081b7e0 , < 581d8bb556dd3e5567bcf322aa5e3e4b6a200c08 (git)
Linux	Linux	Affected: 6.13 Unaffected: 0 , < 6.13 (semver) Unaffected: 7.2.6 , ≤ 7.2.* (semver) Unaffected: 7.3-rc1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/nvme/target/admin-cmd.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "9e136150ac55df4b7ea36e6110ffa39d08905f37",
              "status": "affected",
              "version": "5fd075cdaf3649000677d960fd9e45c08081b7e0",
              "versionType": "git"
            },
            {
              "lessThan": "581d8bb556dd3e5567bcf322aa5e3e4b6a200c08",
              "status": "affected",
              "version": "5fd075cdaf3649000677d960fd9e45c08081b7e0",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/nvme/target/admin-cmd.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.13"
            },
            {
              "lessThan": "6.13",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.6",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix return status of RMI log page on allocation failure\n\nnvmet_execute_get_log_page_rmi() leaves \u0027status\u0027 holding NVME_SC_SUCCESS\n(set by the successful nvmet_req_find_ns() call) when the kzalloc() for\nthe log buffer fails. It then jumps to the out label and completes the\nrequest with a success status, so the host is told the command succeeded\nwhile no data was transferred.\n\nInitialize \u0027status\u0027 to NVME_SC_INTERNAL, matching the smart log handler,\nso an allocation failure is reported as an internal error."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-17T16:09:38.732Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/9e136150ac55df4b7ea36e6110ffa39d08905f37"
        },
        {
          "url": "https://git.kernel.org/stable/c/581d8bb556dd3e5567bcf322aa5e3e4b6a200c08"
        }
      ],
      "title": "nvmet: fix return status of RMI log page on allocation failure",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-90412",
    "datePublished": "2026-09-17T16:09:38.732Z",
    "dateReserved": "2026-09-11T19:38:34.812Z",
    "dateUpdated": "2026-09-17T16:09:38.732Z",
    "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.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

GHSA-C4VG-43J9-MH2M

CVE-2026-90412 (GCVE-0-2026-90412)

Tags

Sightings

Nomenclature

Related by attack behaviour