linux: In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in __close_file_table_...
CVE-2026-74522 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-74522, released August 16, 2026. It is not reported as exploited. Patch Radar priority: High.
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in __close_file_table_ids() A ksmbd_file can remain alive after logical close while another session holds a temporary reference obtained through ksmbd_lookup_fd_inode(). ksmbd_close_fd() currently marks the file closed and drops the idr-owned reference, but leaves the pointer published in the closing session's idr until the final reference is dropped. If the foreign holder performs the final ksmbd_fd_put(), __put_fd_final() supplies the foreign session's file table to __ksmbd_close_fd(). The object is then freed without being removed from its owner's idr, and the owner session later dereferences the stale pointer during file-table teardown. Remove the volatile id from the owner's idr while ksmbd_close_fd() still holds that table's lock, and clear volatile_id before dropping the idr-owned reference. A later foreign final put then only performs physical destruction and cannot remove the object from the wrong table.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| linux · Debian 12.15 (bookworm) | 6.1.187-1 | DEBIAN-CVE-2026-74522 | Aug 16, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.105-1 | DEBIAN-CVE-2026-74522 | Aug 16, 2026 |
| linux · Debian 14 | 7.1.8-1 | DEBIAN-CVE-2026-74522 | Aug 16, 2026 |
| linux-6.12 · Debian 12.15 (bookworm) | 6.12.107-1~deb12u1 | DEBIAN-CVE-2026-74522 | Aug 16, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.