CVE-2026-74472ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 4 days later
· 4 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 6d9e6dfdf3b207701471f364121c67eefb000682 – < 787c944502e7e63d20a9201bada77e0dd924f458
- affected 6d9e6dfdf3b207701471f364121c67eefb000682 – < ee41b00858ca65b4428e99efe39a4277c1f043d2
- affected 6d9e6dfdf3b207701471f364121c67eefb000682 – < b67ce16b26ad0f14cfd6071013840aa95f823bea
- affected 6d9e6dfdf3b207701471f364121c67eefb000682 – < 205feb72e5beb3140e4e1403b6cff30cf739bab9
- affected 6d9e6dfdf3b207701471f364121c67eefb000682 – < 127033b79383a3e78361d7e971588aa8849f5124
- affected 6d9e6dfdf3b207701471f364121c67eefb000682 – < e65848e4ce352bac9e3465099354c8b8f845391f
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.151 – ≤ 6.6.*
- unaffected 6.12.103 – ≤ 6.12.*
- unaffected 6.18.44 – ≤ 6.18.*
- unaffected 7.1.8 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/787c944502e7e63d20a9201bada77e0dd924f458 (opens in a new tab)
- https://git.kernel.org/stable/c/ee41b00858ca65b4428e99efe39a4277c1f043d2 (opens in a new tab)
- https://git.kernel.org/stable/c/b67ce16b26ad0f14cfd6071013840aa95f823bea (opens in a new tab)
- https://git.kernel.org/stable/c/205feb72e5beb3140e4e1403b6cff30cf739bab9 (opens in a new tab)
- https://git.kernel.org/stable/c/127033b79383a3e78361d7e971588aa8849f5124 (opens in a new tab)
- https://git.kernel.org/stable/c/e65848e4ce352bac9e3465099354c8b8f845391f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59665 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74472)Record last updated .