{“lastseen”:””,”description”:”In the Linux kernel, the following vulnerability has been resolved:\\n\\nfs\/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling\\n\\nA SOFTIRQ-safe to SOFTIRQ-unsafe lock order deadlock can occur in\\nsend_sigio() and send_sigurg() when a process group receives a signal.\\n\\nWhen FASYNC is configured for a process group (PIDTYPE_PGID), both\\nfunctions use read_lock(\\u0026tasklist_lock) to traverse the task list.\\nHowever, they are frequently called from softirq context:\\n- send_sigio() via input_inject_event -\\u003e kill_fasync\\n- send_sigurg() via tcp_check_urg -\\u003e sk_send_sigurg (NET_RX_SOFTIRQ)\\n\\nThe deadlock is caused by the rwlock writer fairness mechanism:\\n1. CPU 0 (process context) holds read_lock(\\u0026tasklist_lock) in do_wait().\\n2. CPU 1 (process context) attempts write_lock(\\u0026tasklist_lock) in\\n fork() or exit() and spins, which blocks all new readers.\\n3. CPU 0 is interrupted by a softirq (e.g., TCP URG packet reception).\\n4. The softirq calls send_sigurg() and attempts to acquire\\n read_lock(\\u0026tasklist_lock), deadlocking because CPU 1 is waiting.\\n\\nSince PID hashing and do_each_pid_task() traversals are already\\nRCU-protected, the read_lock on tasklist_lock is no longer strictly\\nrequired for safe traversal. Fix this by replacing tasklist_lock with\\nrcu_read_lock(), aligning the process group signaling path with the\\nsingle-PID path. This also mitigates a potential remote denial of\\nservice vector via TCP URG packets.\\n\\nLockdep splat:\\n=====================================================\\nWARNING: SOFTIRQ-safe -\\u003e SOFTIRQ-unsafe lock order detected\\n[…]\\nChain exists of:\\n \\u0026dev-\\u003eevent_lock –\\u003e \\u0026f_owner-\\u003elock –\\u003e tasklist_lock\\n\\nPossible interrupt unsafe locking scenario:\\n CPU0 CPU1\\n —- —-\\n lock(tasklist_lock);\\n local_irq_disable();\\n lock(\\u0026dev-\\u003eevent_lock);\\n lock(\\u0026f_owner-\\u003elock);\\n \\u003cInterrupt\\u003e\\n lock(\\u0026dev-\\u003eevent_lock);\\n\\n*** DEADLOCK ***”,”published”:”2026-06-24T16:26:04.419Z”,”modified”:”2026-06-28T06:37:04.247Z”,”type”:”cve”,”title”:”fs\/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling”,”source”:”Linux”,”references”:”https:\/\/git.kernel.org\/stable\/c\/54626335ea4174ab2d9a183b511d825f6765e47b\\nhttps:\/\/git.kernel.org\/stable\/c\/897d6a7247739fb1528f98c575df4f2e5de7f994\\nhttps:\/\/git.kernel.org\/stable\/c\/32dbd5ce4be3a3ed7e00f8af18795cc84fc50a33\\nhttps:\/\/git.kernel.org\/stable\/c\/b5fa9e32fb6718f70c986ee14dd5d01b4846f331\\nhttps:\/\/git.kernel.org\/stable\/c\/1bee417678f1135e35b25a37734db46aa94258d2\\nhttps:\/\/git.kernel.org\/stable\/c\/20a93e397abe850c49b6fa0e8cc827b5f634a8f5\\nhttps:\/\/git.kernel.org\/stable\/c\/bfcc8e8d8a495bb34cae9e620adfb75fb13a3954\\nhttps:\/\/git.kernel.org\/stable\/c\/36c1b57b2ecf3c61ac93f5f07bd29b6f21e226ed”,”id”:”CVE-2026-52946″,”bulletinFamily”:””,”cwe”:null,”cvelist”:null,”sourceData”:”Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\\nLinux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\\nLinux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\\nLinux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\\nLinux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\\nLinux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\\nLinux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\\nLinux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\\nLinux Linux 0\\nLinux Linux 0\\nLinux Linux 0\\nLinux Linux 0\\nLinux Linux 0\\nLinux Linux 0\\nLinux Linux 0\\nLinux Linux 0″,”sourceHref”:””,”cvss”:{“score”:7.5,”severity”:”HIGH”,”vector”:”CVSS:3.1\/AV:N\/AC:L\/PR:N\/UI:N\/S:U\/C:N\/I:N\/A:H”,”version”:”3.1″},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:””,”category_name”:”CVE”,”post_link”:””,”product”:”Linux”,”version”:”1da177e4c3f41524e886b7f1b8a0c1fc7321cac2″,”vendor”:”Linux”,”ai_description”:””,”ai_severity”:””,”ai_vendor”:””,”ai_product”:””,”ai_version”:””,”ai_score”:0}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:””,”description”:”In the Linux kernel, the following vulnerability has been resolved:\\n\\nfs\/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling\\n\\nA SOFTIRQ-safe to SOFTIRQ-unsafe lock order deadlock can occur…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[6,8,16,12,15,13,7,11,5],"class_list":["post-66542","post","type-post","status-publish","format-standard","hentry","category-category_cve","tag-cve","tag-cvss","tag-cvss-75","tag-exploit","tag-high","tag-news","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n