https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sun, 10 May 2026 10:54:40 +0000 https://vulnerability.circl.lu/sighting/76b47aa5-9ef0-4731-98ca-49636bab9cfc/export {"uuid": "76b47aa5-9ef0-4731-98ca-49636bab9cfc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22120", "type": "seen", "source": "https://t.me/cvedetector/23123", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-22120 - \"EXT4-fs Linux Kernel Hung Task Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2025-22120 \nPublished : April 16, 2025, 3:16 p.m. | 23\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \next4: goto right label 'out_mmap_sem' in ext4_setattr() \n \nOtherwise, if ext4_inode_attach_jinode() fails, a hung task will \nhappen because filemap_invalidate_unlock() isn't called to unlock \nmapping->invalidate_lock. Like this: \n \nEXT4-fs error (device sda) in ext4_setattr:5557: Out of memory \nINFO: task fsstress:374 blocked for more than 122 seconds. \n Not tainted 6.14.0-rc1-next-20250206-xfstests-dirty #726 \n\"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. \ntask:fsstress state:D stack:0 pid:374 tgid:374 ppid:373 \n task_flags:0x440140 flags:0x00000000 \nCall Trace: \n \n __schedule+0x2c9/0x7f0 \n schedule+0x27/0xa0 \n schedule_preempt_disabled+0x15/0x30 \n rwsem_down_read_slowpath+0x278/0x4c0 \n down_read+0x59/0xb0 \n page_cache_ra_unbounded+0x65/0x1b0 \n filemap_get_pages+0x124/0x3e0 \n filemap_read+0x114/0x3d0 \n vfs_read+0x297/0x360 \n ksys_read+0x6c/0xe0 \n do_syscall_64+0x4b/0x110 \n entry_SYSCALL_64_after_hwframe+0x76/0x7e \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T17:43:49.000000Z"} {"uuid": "76b47aa5-9ef0-4731-98ca-49636bab9cfc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22120", "type": "seen", "source": "https://t.me/cvedetector/23123", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-22120 - \"EXT4-fs Linux Kernel Hung Task Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2025-22120 \nPublished : April 16, 2025, 3:16 p.m. | 23\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \next4: goto right label 'out_mmap_sem' in ext4_setattr() \n \nOtherwise, if ext4_inode_attach_jinode() fails, a hung task will \nhappen because filemap_invalidate_unlock() isn't called to unlock \nmapping->invalidate_lock. Like this: \n \nEXT4-fs error (device sda) in ext4_setattr:5557: Out of memory \nINFO: task fsstress:374 blocked for more than 122 seconds. \n Not tainted 6.14.0-rc1-next-20250206-xfstests-dirty #726 \n\"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. \ntask:fsstress state:D stack:0 pid:374 tgid:374 ppid:373 \n task_flags:0x440140 flags:0x00000000 \nCall Trace: \n \n __schedule+0x2c9/0x7f0 \n schedule+0x27/0xa0 \n schedule_preempt_disabled+0x15/0x30 \n rwsem_down_read_slowpath+0x278/0x4c0 \n down_read+0x59/0xb0 \n page_cache_ra_unbounded+0x65/0x1b0 \n filemap_get_pages+0x124/0x3e0 \n filemap_read+0x114/0x3d0 \n vfs_read+0x297/0x360 \n ksys_read+0x6c/0xe0 \n do_syscall_64+0x4b/0x110 \n entry_SYSCALL_64_after_hwframe+0x76/0x7e \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T17:43:49.000000Z"} https://vulnerability.circl.lu/sighting/76b47aa5-9ef0-4731-98ca-49636bab9cfc/export Wed, 16 Apr 2025 17:43:49 +0000