CVE-2026-74472

CVE CVE-2026-74472EUVD EUVD-2026-59665Veröffentlicht 2026-08-15T12:27:08.000ZZuletzt geändert 2026-08-19T16:37:23.000Z

Was das Advisory beschreibt

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.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux 6d9e6dfdf3b207701471f364121c67eefb000682 <205feb72e5beb3140e4e1403b6cff30cf739bab9; 6.0; 6d9e6dfdf3b207701471f364121c67eefb000682 <127033b79383a3e78361d7e971588aa8849f5124; 6d9e6dfdf3b207701471f364121c67eefb000682 <787c944502e7e63d20a9201bada77e0dd924f458; patch: 6.12.103; 6d9e6dfdf3b207701471f364121c67eefb000682 <ee41b00858ca65b4428e99efe39a4277c1f043d2; patch: 7.2; patch: 7.1.8; patch: 6.6.151; patch: 6.1.183; 6d9e6dfdf3b207701471f364121c67eefb000682 <b67ce16b26ad0f14cfd6071013840aa95f823bea; patch: 0; 6d9e6dfdf3b207701471f364121c67eefb000682 <e65848e4ce352bac9e3465099354c8b8f845391f; patch: 6.18.44

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.