CVE-2026-74259

CVE CVE-2026-74259EUVD EUVD-2026-59406Published 2026-08-15T05:57:36.000ZLast changed 2026-08-17T05:45:08.000ZCVSS 8.4

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: cifs: remove all cifs files before kill super Cifs files may be put into fileinfo_put_wq during umounting cifs. After umount done, cifsFileInfo_put_final is called, which cause following BUG: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... [ 134.222152] list_lru_add+0x64/0x1a0 [ 134.222399] ? cifs_put_tcon+0x171/0x340 [cifs] [ 134.222772] d_lru_add+0x44/0x60 [ 134.222997] dput+0x1fc/0x210 [ 134.223213] cifsFileInfo_put_final+0x11a/0x140 [cifs] [ 134.223576] process_one_work+0x17c/0x320 [ 134.223843] worker_thread+0x188/0x280 [ 134.224084] ? __pfx_worker_thread+0x10/0x10 [ 134.224366] kthread+0xcc/0x100 [ 134.224576] ? __pfx_kthread+0x10/0x10 [ 134.224827] ret_from_fork+0x30/0x50 [ 134.225063] ? __pfx_kthread+0x10/0x10 [ 134.225328] ret_from_fork_asm+0x1b/0x30 This can be reproduce by following: unshare -n bash -c " mkdir -p ${CIFS_MNT} ip netns attach root 1 ip link add eth0 type veth peer veth0 netns root ip link set eth0 up ip -n root link set veth0 up ip addr add 192.168.0.2/24 dev eth0 ip -n root addr add 192.168.0.1/24 dev veth0 ip route add default via 192.168.0.1 dev eth0 ip netns exec root sysctl net.ipv4.ip_forward=1 ip netns exec root iptables -t nat -A POSTROUTING -s 192.168.0.2 -o ${DEV} -j MASQUERADE mount -t cifs ${CIFS_PATH} ${CIFS_MNT} -o vers=3.0,sec=ntlmssp,credentials=${CIFS_CRED},rsize=65536,wsize=65536,cache=none,echo_interval=1 touch ${CIFS_MNT}/a.txt ip netns exec root iptables -t nat -D POSTROUTING -s 192.168.0.2 -o ${DEV} -j MASQUERADE " umount ${CIFS_MNT}

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.1.5; patch: 6.6.145; 6.1.167 <6.1.178; 340cea84f691c5206561bb2e0147158fe02070be <7839f1817a0cb6c4ed5cfe25d04845c43380a129; 7.0; f655467a9973f964b267871e5fef533ad5014494 <21303c4a2b7275e626c6b67de0f45f2d5b9bb3e7; 708c276f516d27beaded7f372ac8111cee43926c <55fb9581986141659002264fdc75cef307811eb8; 6.12.78 <6.12.97; patch: 6.1.178; 6.18.20 <6.18.40; 30afc6ea72cc6cf7c8d579e79b64232801c38d08; 6.19.10 <6.20; patch: 6.18.40; 340cea84f691c5206561bb2e0147158fe02070be <6d9a4aaaa8b2612b5ef9d581e2f286a458b71ee1; 0e4b8faaaebe3137bec5723ef2b3cb0437fb38fd <3baedc9b2f53e6a6ac57b16fdff0f9b954d9ca71; patch: 7.2; 0629a1a187e424373364d681b42b101894bdb548 <4465ebe67d89345954bb3622b25dd13e06f9d367; patch: 0; patch: 6.12.97; 6.6.130 <6.6.145

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.