{"dataType": "CVE_RECORD", "dataVersion": "5.1", "cveMetadata": {"cveId": "CVE-2025-21837", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2024-12-29T08:45:45.777Z", "datePublished": "2025-03-07T09:09:56.827Z", "dateUpdated": "2025-03-24T15:41:09.740Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2025-03-24T15:41:09.740Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/uring_cmd: unconditionally copy SQEs at prep time\n\nThis isn't 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."}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["io_uring/uring_cmd.c"], "versions": [{"version": "5eff57fa9f3aae3acbcaf196af507eec58955f3b", "lessThan": "87fe1d68842a308998b315c8ed0163a1d639017c", "status": "affected", "versionType": "git"}, {"version": "5eff57fa9f3aae3acbcaf196af507eec58955f3b", "lessThan": "d6211ebbdaa541af197b50b8dd8f22642ce0b87f", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["io_uring/uring_cmd.c"], "versions": [{"version": "6.10", "status": "affected"}, {"version": "0", "lessThan": "6.10", "status": "unaffected", "versionType": "semver"}, {"version": "6.13.4", "lessThanOrEqual": "6.13.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.14", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "references": [{"url": "https://git.kernel.org/stable/c/87fe1d68842a308998b315c8ed0163a1d639017c"}, {"url": "https://git.kernel.org/stable/c/d6211ebbdaa541af197b50b8dd8f22642ce0b87f"}], "title": "io_uring/uring_cmd: unconditionally copy SQEs at prep time", "x_generator": {"engine": "bippy-5f407fcff5a0"}}}}

{}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/uring_cmd: unconditionally copy SQEs at prep time\n\nThis isn't 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": "CVE-2025-21837", "lastModified": "2025-03-07T09:15:16.710", "metrics": {}, "published": "2025-03-07T09:15:16.710", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/87fe1d68842a308998b315c8ed0163a1d639017c"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/d6211ebbdaa541af197b50b8dd8f22642ce0b87f"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: io_uring/uring_cmd: unconditionally copy SQEs at prep time", "id": "2350589", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2350589"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "details": ["In the Linux kernel, the following vulnerability has been resolved:\nio_uring/uring_cmd: unconditionally copy SQEs at prep time\nThis isn't 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.\nDown the line we can relax this again once uring_cmd has been sanitized\na bit, and avoid unnecessarily copying the SQE."], "name": "CVE-2025-21837", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2025-03-07T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2025-21837\nhttps://nvd.nist.gov/vuln/detail/CVE-2025-21837\nhttps://lore.kernel.org/linux-cve-announce/2025030706-CVE-2025-21837-85ef@gregkh/T"], "threat_severity": "Important"}