{"id":"CVE-2026-99671","summary":"can: raw, isotp: copy socket options outside of lock_sock()","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ncan: raw, isotp: copy socket options outside of lock_sock()\n\nThe CAN_RAW and CAN_ISOTP specific socket options are copied from and\nto user space while holding lock_sock(). A copy that faults or stalls,\ne.g. on a userfaultfd or FUSE backed mapping, holds lock_sock() for its\nwhole duration.\n\nraw_notify() and isotp_notify() take lock_sock() of a socket that is\nbound to the vanishing device while holding RTNL. As the CAN_RAW\noptions can also be changed on a bound socket, a stalled copy can block\nRTNL on an unregistration or namespace change of the bound device.\nBefore \"can: protect the receive lists with a per-device lock\",\nraw_setsockopt() even held RTNL itself during the copy. CAN_ISOTP only\ncopies its options for unbound sockets, which isotp_notify() skips\nwithout taking lock_sock().\n\nKeep the user space copies out of the locked sections: Check the option\nname and length and copy the option values, including the CAN_RAW_FILTER\nfilters, to kernel memory before lock_sock(). raw_setsockopt_locked()\nand isotp_setsockopt_locked() get the copied values directly and drop\ntheir now redundant length checks and copies. As a side effect, a\nfailing copy can not leave partially overwritten options behind\nanymore. In raw_getsockopt() duplicate the filters under lock_sock() and\ncopy them to user space after release_sock().\n\nAs the option name and length are now checked before lock_sock(), the\norder of the checks in isotp_setsockopt() and accordingly the order of\nthe returned error values changes. This is in line with POSIX, which\ndoes not define an order in which multiple error conditions are\ndetected and reported.\n\nThe generic SOL_SOCKET options in sk_setsockopt() are not affected by\nthis patch.","modified":"2026-11-20T07:01:08.569338513Z","published":"2026-11-20T05:50:20.377Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99671.json","cna_assigner":"Linux"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/12b2ddd7d01b7e5ec466c128ff862197d59c2440"},{"type":"WEB","url":"https://git.kernel.org/stable/c/233eb0922c17063911dd4e947ef91ef5125b9665"},{"type":"WEB","url":"https://git.kernel.org/stable/c/43c973a0887d3d7b2ee0a446603c97bf0f38c58e"},{"type":"WEB","url":"https://git.kernel.org/stable/c/ecc81d48ae70513db45de567ae164a1993b792c5"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99671.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99671"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"c18ce101f2e47d97ace125033e2896895a6db3dd"},{"fixed":"ecc81d48ae70513db45de567ae164a1993b792c5"},{"fixed":"233eb0922c17063911dd4e947ef91ef5125b9665"},{"fixed":"12b2ddd7d01b7e5ec466c128ff862197d59c2440"},{"fixed":"43c973a0887d3d7b2ee0a446603c97bf0f38c58e"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99671.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.25"},{"fixed":"6.12.118"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.64"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.3.5"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99671.json"}}],"schema_version":"1.9.2"}