ghsa-qm29-hj4p-276m
Vulnerability from github
Published
2025-03-07 09:30
Modified
2025-03-07 09:30
Details

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

io_uring/uring_cmd: unconditionally copy SQEs at prep time

This isn't generally necessary, but conditions have been observed where SQE data is accessed from the original SQE after prep has been done and outside of the initial issue. Opcode prep handlers must ensure that any SQE related data is stable beyond the prep phase, but uring_cmd is a bit special in how it handles the SQE which makes it susceptible to reading stale data. If the application has reused the SQE before the original completes, then that can lead to data corruption.

Down the line we can relax this again once uring_cmd has been sanitized a bit, and avoid unnecessarily copying the SQE.

Show details on source website

To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-21837"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-03-07T09:15:16Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/uring_cmd: unconditionally copy SQEs at prep time\n\nThis isn\u0027t generally necessary, but conditions have been observed where\nSQE data is accessed from the original SQE after prep has been done and\noutside of the initial issue. Opcode prep handlers must ensure that any\nSQE related data is stable beyond the prep phase, but uring_cmd is a bit\nspecial in how it handles the SQE which makes it susceptible to reading\nstale data. If the application has reused the SQE before the original\ncompletes, then that can lead to data corruption.\n\nDown the line we can relax this again once uring_cmd has been sanitized\na bit, and avoid unnecessarily copying the SQE.",
  "id": "GHSA-qm29-hj4p-276m",
  "modified": "2025-03-07T09:30:35Z",
  "published": "2025-03-07T09:30:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-21837"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/87fe1d68842a308998b315c8ed0163a1d639017c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d6211ebbdaa541af197b50b8dd8f22642ce0b87f"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.