{"api_version":"1","generated_at":"2026-08-16T09:26:33+00:00","cve":"CVE-2026-74472","urls":{"html":"https://cve.report/CVE-2026-74472","api":"https://cve.report/api/cve/CVE-2026-74472.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74472","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74472"},"summary":{"title":"ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()\n\nublk_ctrl_add_dev() memcpy()s the userspace ublksrv_ctrl_dev_info into\nub->dev_info and then fixes up the fields the driver owns, but misses\n->state and ->ublksrv_pid.\n\nA device added with ->state = UBLK_S_DEV_LIVE passes the\n\"->state != UBLK_S_DEV_DEAD\" test that ublk_stop_dev_unlocked() uses as its\nproxy for \"a disk is attached\", while ->ub_disk is still NULL, so DEL_DEV\nright after ADD_DEV oopses in del_gendisk().  UBLK_S_DEV_QUIESCED plus\nUBLK_F_USER_RECOVERY dies one step earlier, in ublk_force_abort_dev().  A\npoisoned ->state also gets START_USER_RECOVERY and the char device\nread/write path onto a device that was never started, and wedges START_DEV\nat -EEXIST.  A poisoned ->ublksrv_pid just makes GET_DEV_INFO report an\nunrelated task as the ublk server.\n\nReset both after the memcpy(), as ublk_detach_disk() does.  Userspace only\never reads these back, so correcting them silently breaks nothing.\n\nADD_DEV has copied ->state in unsanitized since ublk was merged, but back\nthen it was harmless: the gendisk was allocated during ADD_DEV, and both\nteardown and the START_DEV -EEXIST check keyed off disk_live() rather than\n->state.  The oops became reachable once the disk allocation moved to\nSTART_DEV and those checks switched to ->state.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 13:17:51","updated_at":"2026-08-15 13:17:51"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/205feb72e5beb3140e4e1403b6cff30cf739bab9","name":"https://git.kernel.org/stable/c/205feb72e5beb3140e4e1403b6cff30cf739bab9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ee41b00858ca65b4428e99efe39a4277c1f043d2","name":"https://git.kernel.org/stable/c/ee41b00858ca65b4428e99efe39a4277c1f043d2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e65848e4ce352bac9e3465099354c8b8f845391f","name":"https://git.kernel.org/stable/c/e65848e4ce352bac9e3465099354c8b8f845391f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/127033b79383a3e78361d7e971588aa8849f5124","name":"https://git.kernel.org/stable/c/127033b79383a3e78361d7e971588aa8849f5124","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b67ce16b26ad0f14cfd6071013840aa95f823bea","name":"https://git.kernel.org/stable/c/b67ce16b26ad0f14cfd6071013840aa95f823bea","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74472","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74472","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6d9e6dfdf3b207701471f364121c67eefb000682 ee41b00858ca65b4428e99efe39a4277c1f043d2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6d9e6dfdf3b207701471f364121c67eefb000682 b67ce16b26ad0f14cfd6071013840aa95f823bea git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6d9e6dfdf3b207701471f364121c67eefb000682 205feb72e5beb3140e4e1403b6cff30cf739bab9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6d9e6dfdf3b207701471f364121c67eefb000682 127033b79383a3e78361d7e971588aa8849f5124 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6d9e6dfdf3b207701471f364121c67eefb000682 e65848e4ce352bac9e3465099354c8b8f845391f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.151 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.103 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.44 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.8 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc6 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/block/ublk_drv.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"ee41b00858ca65b4428e99efe39a4277c1f043d2","status":"affected","version":"6d9e6dfdf3b207701471f364121c67eefb000682","versionType":"git"},{"lessThan":"b67ce16b26ad0f14cfd6071013840aa95f823bea","status":"affected","version":"6d9e6dfdf3b207701471f364121c67eefb000682","versionType":"git"},{"lessThan":"205feb72e5beb3140e4e1403b6cff30cf739bab9","status":"affected","version":"6d9e6dfdf3b207701471f364121c67eefb000682","versionType":"git"},{"lessThan":"127033b79383a3e78361d7e971588aa8849f5124","status":"affected","version":"6d9e6dfdf3b207701471f364121c67eefb000682","versionType":"git"},{"lessThan":"e65848e4ce352bac9e3465099354c8b8f845391f","status":"affected","version":"6d9e6dfdf3b207701471f364121c67eefb000682","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/block/ublk_drv.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.0"},{"lessThan":"6.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.151","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.103","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.44","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.8","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc6","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.151","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.103","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.44","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.8","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc6","versionStartIncluding":"6.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()\n\nublk_ctrl_add_dev() memcpy()s the userspace ublksrv_ctrl_dev_info into\nub->dev_info and then fixes up the fields the driver owns, but misses\n->state and ->ublksrv_pid.\n\nA device added with ->state = UBLK_S_DEV_LIVE passes the\n\"->state != UBLK_S_DEV_DEAD\" test that ublk_stop_dev_unlocked() uses as its\nproxy for \"a disk is attached\", while ->ub_disk is still NULL, so DEL_DEV\nright after ADD_DEV oopses in del_gendisk().  UBLK_S_DEV_QUIESCED plus\nUBLK_F_USER_RECOVERY dies one step earlier, in ublk_force_abort_dev().  A\npoisoned ->state also gets START_USER_RECOVERY and the char device\nread/write path onto a device that was never started, and wedges START_DEV\nat -EEXIST.  A poisoned ->ublksrv_pid just makes GET_DEV_INFO report an\nunrelated task as the ublk server.\n\nReset both after the memcpy(), as ublk_detach_disk() does.  Userspace only\never reads these back, so correcting them silently breaks nothing.\n\nADD_DEV has copied ->state in unsanitized since ublk was merged, but back\nthen it was harmless: the gendisk was allocated during ADD_DEV, and both\nteardown and the START_DEV -EEXIST check keyed off disk_live() rather than\n->state.  The oops became reachable once the disk allocation moved to\nSTART_DEV and those checks switched to ->state."}],"providerMetadata":{"dateUpdated":"2026-08-15T12:27:08.759Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/ee41b00858ca65b4428e99efe39a4277c1f043d2"},{"url":"https://git.kernel.org/stable/c/b67ce16b26ad0f14cfd6071013840aa95f823bea"},{"url":"https://git.kernel.org/stable/c/205feb72e5beb3140e4e1403b6cff30cf739bab9"},{"url":"https://git.kernel.org/stable/c/127033b79383a3e78361d7e971588aa8849f5124"},{"url":"https://git.kernel.org/stable/c/e65848e4ce352bac9e3465099354c8b8f845391f"}],"title":"ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74472","datePublished":"2026-08-15T12:27:08.759Z","dateReserved":"2026-08-15T05:44:03.902Z","dateUpdated":"2026-08-15T12:27:08.759Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 13:17:51","lastModifiedDate":"2026-08-15 13:17:51","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74472","Ordinal":"1","Title":"ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()","CVE":"CVE-2026-74472","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74472","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()\n\nublk_ctrl_add_dev() memcpy()s the userspace ublksrv_ctrl_dev_info into\nub->dev_info and then fixes up the fields the driver owns, but misses\n->state and ->ublksrv_pid.\n\nA device added with ->state = UBLK_S_DEV_LIVE passes the\n\"->state != UBLK_S_DEV_DEAD\" test that ublk_stop_dev_unlocked() uses as its\nproxy for \"a disk is attached\", while ->ub_disk is still NULL, so DEL_DEV\nright after ADD_DEV oopses in del_gendisk().  UBLK_S_DEV_QUIESCED plus\nUBLK_F_USER_RECOVERY dies one step earlier, in ublk_force_abort_dev().  A\npoisoned ->state also gets START_USER_RECOVERY and the char device\nread/write path onto a device that was never started, and wedges START_DEV\nat -EEXIST.  A poisoned ->ublksrv_pid just makes GET_DEV_INFO report an\nunrelated task as the ublk server.\n\nReset both after the memcpy(), as ublk_detach_disk() does.  Userspace only\never reads these back, so correcting them silently breaks nothing.\n\nADD_DEV has copied ->state in unsanitized since ublk was merged, but back\nthen it was harmless: the gendisk was allocated during ADD_DEV, and both\nteardown and the START_DEV -EEXIST check keyed off disk_live() rather than\n->state.  The oops became reachable once the disk allocation moved to\nSTART_DEV and those checks switched to ->state.","Type":"Description","Title":"ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()"}]}}}