ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()
Summary
| CVE | CVE-2026-74472 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 13:17:51 UTC |
| Updated | 2026-08-19 17:21:04 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev() ublk_ctrl_add_dev() memcpy()s the userspace ublksrv_ctrl_dev_info into ub->dev_info and then fixes up the fields the driver owns, but misses ->state and ->ublksrv_pid. A device added with ->state = UBLK_S_DEV_LIVE passes the "->state != UBLK_S_DEV_DEAD" test that ublk_stop_dev_unlocked() uses as its proxy for "a disk is attached", while ->ub_disk is still NULL, so DEL_DEV right after ADD_DEV oopses in del_gendisk(). UBLK_S_DEV_QUIESCED plus UBLK_F_USER_RECOVERY dies one step earlier, in ublk_force_abort_dev(). A poisoned ->state also gets START_USER_RECOVERY and the char device read/write path onto a device that was never started, and wedges START_DEV at -EEXIST. A poisoned ->ublksrv_pid just makes GET_DEV_INFO report an unrelated task as the ublk server. Reset both after the memcpy(), as ublk_detach_disk() does. Userspace only ever reads these back, so correcting them silently breaks nothing. ADD_DEV has copied ->state in unsanitized since ublk was merged, but back then it was harmless: the gendisk was allocated during ADD_DEV, and both teardown and the START_DEV -EEXIST check keyed off disk_live() rather than ->state. The oops became reachable once the disk allocation moved to START_DEV and those checks switched to ->state. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.065340000 (date 2026-08-19)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 6d9e6dfdf3b207701471f364121c67eefb000682 787c944502e7e63d20a9201bada77e0dd924f458 git | Not specified |
| CNA | Linux | Linux | affected 6d9e6dfdf3b207701471f364121c67eefb000682 ee41b00858ca65b4428e99efe39a4277c1f043d2 git | Not specified |
| CNA | Linux | Linux | affected 6d9e6dfdf3b207701471f364121c67eefb000682 b67ce16b26ad0f14cfd6071013840aa95f823bea git | Not specified |
| CNA | Linux | Linux | affected 6d9e6dfdf3b207701471f364121c67eefb000682 205feb72e5beb3140e4e1403b6cff30cf739bab9 git | Not specified |
| CNA | Linux | Linux | affected 6d9e6dfdf3b207701471f364121c67eefb000682 127033b79383a3e78361d7e971588aa8849f5124 git | Not specified |
| CNA | Linux | Linux | affected 6d9e6dfdf3b207701471f364121c67eefb000682 e65848e4ce352bac9e3465099354c8b8f845391f git | Not specified |
| CNA | Linux | Linux | affected 6.0 | Not specified |
| CNA | Linux | Linux | unaffected 6.0 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.183 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.151 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.103 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.44 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.8 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/787c944502e7e63d20a9201bada77e0dd924f458 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/205feb72e5beb3140e4e1403b6cff30cf739bab9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ee41b00858ca65b4428e99efe39a4277c1f043d2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e65848e4ce352bac9e3465099354c8b8f845391f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/127033b79383a3e78361d7e971588aa8849f5124 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b67ce16b26ad0f14cfd6071013840aa95f823bea | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.