CVE-2026-64317

CVE CVE-2026-64317EUVD EUVD-2026-49029Veröffentlicht 2026-07-25T08:49:47.000ZZuletzt geändert 2026-08-05T12:40:54.000ZCVSS 7.1

Was das Advisory beschreibt

In the Linux kernel, the following vulnerability has been resolved: isofs: bound Rock Ridge symlink components to the SL record get_symlink_chunk() and the SL handling in parse_rock_ridge_inode_internal() walk the variable-length components of a Rock Ridge "SL" (symbolic link) record. Each component is a two-byte header (flags, len) followed by len bytes of text, so it occupies slp->len + 2 bytes. Both loops read slp->len and advance to the next component, and get_symlink_chunk() additionally does memcpy(rpnt, slp->text, slp->len), but neither checks that the component lies within the SL record before dereferencing it. A crafted SL record whose component declares a len that runs past the record (rr->len) therefore triggers an out-of-bounds read of up to 255 bytes. When the record sits at the tail of its backing buffer - for example a small kmalloc()ed continuation block reached through a CE record - the read crosses the allocation; get_symlink_chunk() then copies the out-of-bounds bytes into the symlink body returned to user space by readlink(), disclosing adjacent kernel memory. ISO 9660 images are routinely mounted from untrusted removable media - desktop environments auto-mount them (e.g. via udisks2) without CAP_SYS_ADMIN - so the record contents are attacker-controlled. Reject any component that does not fit in the remaining record bytes before using it. In get_symlink_chunk() return NULL, like the existing output-buffer (plimit) checks, so a malformed record makes readlink() fail with -EIO rather than silently returning a truncated target; in parse_rock_ridge_inode_internal() stop the inode-size walk.

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 patch: 7.1.4; 2.6.12; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5fa1d6a5ec2356d2107dead614437c66fa7138b1; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a22cb6bb54dc167047ea9e70d97dfbc2c15649e3; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <36fe7d25dbc40da0c6b1dd4513a4f69ac6164eee; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b5699642640d6cff357638738c5293985cd5a53d; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1015e1c4b2fadd9c09704e24738e46598778c869; patch: 6.6.145; patch: 6.12.96; patch: 5.15.212; patch: 6.1.178; patch: 6.18.39; patch: 5.10.261; patch: 0; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9830725078c8483c6831ec10222ae724806ea36b; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6bf41db09ef935d76fcc84ccf213b42c18de95ee; patch: 7.2-rc1; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b736b12108fd116c41777628f5a333791604df26

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.