Vulnerability-Lookup

GHSA-95F6-3PP2-9382

Vulnerability from github – Published: 2026-10-18 18:32 – Updated: 2026-10-18 18:32

Details

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

blk-mq: set RQF_USE_SCHED when the operation is known

The cached requests are allocated for one operation but can be handed out for another. A passthrough command has RQF_USE_SCHED cleared, so using those flags for a subsequent read/write bio will insert it into the scheduler without ->prepare_request() and frees it without ->finish_request(). For kyber, this leaks the domain token acquired at dispatch and stalls the queue.

Don't set RQF_USE_SCHED based on the first operation the batch happened to be allocated for. Instead, set it after the request is claimed by an operation. Introduce a helper function, blk_mq_rq_late_init() for this, and absorb blk_mq_rq_time_init() since the two run together.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-98820"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-18T16:17:36Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-mq: set RQF_USE_SCHED when the operation is known\n\nThe cached requests are allocated for one operation but can be handed\nout for another. A passthrough command has RQF_USE_SCHED cleared, so\nusing those flags for a subsequent read/write bio will insert it into\nthe scheduler without -\u003eprepare_request() and frees it without\n-\u003efinish_request(). For kyber, this leaks the domain token acquired at\ndispatch and stalls the queue.\n\nDon\u0027t set RQF_USE_SCHED based on the first operation the batch happened\nto be allocated for. Instead, set it after the request is claimed by an\noperation. Introduce a helper function, blk_mq_rq_late_init() for this,\nand absorb blk_mq_rq_time_init() since the two run together.",
  "id": "GHSA-95f6-3pp2-9382",
  "modified": "2026-10-18T18:32:04Z",
  "published": "2026-10-18T18:32:04Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98820"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2c47ebc27fa72078e26177cd458cdaf3006a9685"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/790730e4d95de8356a573d4b4864486bba731863"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ab6c756f28c741d704a7c3e04814bfc3adf6f818"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-98820 (GCVE-0-2026-98820)

Vulnerability from cvelistv5 – Published: 2026-10-18 15:49 – Updated: 2026-10-19 09:26

Title

blk-mq: set RQF_USE_SCHED when the operation is known

Summary

In the Linux kernel, the following vulnerability has been resolved: blk-mq: set RQF_USE_SCHED when the operation is known The cached requests are allocated for one operation but can be handed out for another. A passthrough command has RQF_USE_SCHED cleared, so using those flags for a subsequent read/write bio will insert it into the scheduler without ->prepare_request() and frees it without ->finish_request(). For kyber, this leaks the domain token acquired at dispatch and stalls the queue. Don't set RQF_USE_SCHED based on the first operation the batch happened to be allocated for. Instead, set it after the request is claimed by an operation. Introduce a helper function, blk_mq_rq_late_init() for this, and absorb blk_mq_rq_time_init() since the two run together.

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6847 records in the last 180 days details

References

3 references

URL	Tags
https://git.kernel.org/stable/c/790730e4d95de8356…
https://git.kernel.org/stable/c/2c47ebc27fa72078e…
https://git.kernel.org/stable/c/ab6c756f28c741d70…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 4b6a5d9cea911424e84107df8c4eb8317938d2cd , < 790730e4d95de8356a573d4b4864486bba731863 (git) Affected: 4b6a5d9cea911424e84107df8c4eb8317938d2cd , < 2c47ebc27fa72078e26177cd458cdaf3006a9685 (git) Affected: 4b6a5d9cea911424e84107df8c4eb8317938d2cd , < ab6c756f28c741d704a7c3e04814bfc3adf6f818 (git)
Linux	Linux	Affected: 6.1 Unaffected: 0 , < 6.1 (semver) Unaffected: 6.18.56 , ≤ 6.18.* (semver) Unaffected: 7.2.10 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "block/blk-mq.c",
            "block/mq-deadline.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "790730e4d95de8356a573d4b4864486bba731863",
              "status": "affected",
              "version": "4b6a5d9cea911424e84107df8c4eb8317938d2cd",
              "versionType": "git"
            },
            {
              "lessThan": "2c47ebc27fa72078e26177cd458cdaf3006a9685",
              "status": "affected",
              "version": "4b6a5d9cea911424e84107df8c4eb8317938d2cd",
              "versionType": "git"
            },
            {
              "lessThan": "ab6c756f28c741d704a7c3e04814bfc3adf6f818",
              "status": "affected",
              "version": "4b6a5d9cea911424e84107df8c4eb8317938d2cd",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "block/blk-mq.c",
            "block/mq-deadline.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.1"
            },
            {
              "lessThan": "6.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.56",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.56",
                  "versionStartIncluding": "6.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.10",
                  "versionStartIncluding": "6.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-mq: set RQF_USE_SCHED when the operation is known\n\nThe cached requests are allocated for one operation but can be handed\nout for another. A passthrough command has RQF_USE_SCHED cleared, so\nusing those flags for a subsequent read/write bio will insert it into\nthe scheduler without -\u003eprepare_request() and frees it without\n-\u003efinish_request(). For kyber, this leaks the domain token acquired at\ndispatch and stalls the queue.\n\nDon\u0027t set RQF_USE_SCHED based on the first operation the batch happened\nto be allocated for. Instead, set it after the request is claimed by an\noperation. Introduce a helper function, blk_mq_rq_late_init() for this,\nand absorb blk_mq_rq_time_init() since the two run together."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T09:26:13.210Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/790730e4d95de8356a573d4b4864486bba731863"
        },
        {
          "url": "https://git.kernel.org/stable/c/2c47ebc27fa72078e26177cd458cdaf3006a9685"
        },
        {
          "url": "https://git.kernel.org/stable/c/ab6c756f28c741d704a7c3e04814bfc3adf6f818"
        }
      ],
      "title": "blk-mq: set RQF_USE_SCHED when the operation is known",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-98820",
    "datePublished": "2026-10-18T15:49:12.251Z",
    "dateReserved": "2026-09-25T10:25:14.372Z",
    "dateUpdated": "2026-10-19T09:26:13.210Z",
    "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.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

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