[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2025-40237":6},{"stargazers_count":4,"fetched_at":5},8,"2026-09-19T04:32:17.889Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":33},"DEBIAN-CVE-2025-40237","In the Linux kernel, the following vulnerability has been resolved:  fs/notify: call exportfs_encode_fid with s_umount  Calling intotify_show_fdinfo() on fd watching an overlayfs inode, while the overlayfs is being unmounted, can lead to dereferencing NULL ptr.  This issue was found by syzkaller.  Race Condition Diagram:  Thread 1                           Thread 2 --------                           --------  generic_shutdown_super()  shrink_dcache_for_umount   sb->s_root = NULL                      |                     |             vfs_read()                     |              inotify_fdinfo()                     |               * inode get from mark *                     |               show_mark_fhandle(m, inode)                     |                exportfs_encode_fid(inode, ..)                     |                 ovl_encode_fh(inode, ..)                     |                  ovl_check_encode_origin(inode)                     |                   * deref i_sb->s_root *                     |                     |                     v  fsnotify_sb_delete(sb)  Which then leads to:  [   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI [   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037] [   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)  \u003Csnip registers, unreliable trace>  [   32.143353] Call Trace: [   32.143732]  ovl_encode_fh+0xd5/0x170 [   32.144031]  exportfs_encode_inode_fh+0x12f/0x300 [   32.144425]  show_mark_fhandle+0xbe/0x1f0 [   32.145805]  inotify_fdinfo+0x226/0x2d0 [   32.146442]  inotify_show_fdinfo+0x1c5/0x350 [   32.147168]  seq_show+0x530/0x6f0 [   32.147449]  seq_read_iter+0x503/0x12a0 [   32.148419]  seq_read+0x31f/0x410 [   32.150714]  vfs_read+0x1f0/0x9e0 [   32.152297]  ksys_read+0x125/0x240  IOW ovl_check_encode_origin derefs inode->i_sb->s_root, after it was set to NULL in the unmount path.  Fix it by protecting calling exportfs_encode_fid() from show_mark_fhandle() with s_umount lock.  This form of fix was suggested by Amir in [1].  [1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/",null,[],[],[],[14],{"_key":15},"CVE-2025-40237",[],[],[],"2025-12-04T16:16:16.697Z","2026-06-15T18:48:39.467689936Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2025-40237",[27],"osv_debian",[29],"Advisory",[],[],[],[34],{"ecosystem":35,"name":36,"vendor":37,"product":36,"cpe_part":9,"purl_type":38,"purl_namespace":37,"purl_name":36,"source":9,"versions":39},"Debian","linux","debian","deb",[40,46],{"version":41,"is_range":42,"range_type":43,"version_start":9,"version_start_type":9,"version_end":44,"version_end_type":45,"fixed_in":9},"lt6_12_57_1",true,"ecosystem","6.12.57-1","excluding",{"version":47,"is_range":42,"range_type":43,"version_start":9,"version_start_type":9,"version_end":48,"version_end_type":45,"fixed_in":9},"lt6_17_6_1","6.17.6-1"]