CVE-2026-52946fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling
- 7.5HighCVSS base score
- 0.47%Exploitation in 30 daysEPSS · top 59% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling A SOFTIRQ-safe to SOFTIRQ-unsafe lock order deadlock can occur in send_sigio() and send_sigurg() when a process group receives a signal. When FASYNC is configured for a process group (PIDTYPE_PGID), both functions use read_lock(&tasklist_lock) to traverse the task list. However, they are frequently called from softirq context: - send_sigio() via input_inject_event -> kill_fasync - send_sigurg() via tcp_check_urg -> sk_send_sigurg (NET_RX_SOFTIRQ) The deadlock is caused by the rwlock writer fairness mechanism: 1. CPU 0 (process context) holds read_lock(&tasklist_lock) in do_wait(). 2. CPU 1 (process context) attempts write_lock(&tasklist_lock) in fork() or exit() and spins, which blocks all new readers. 3. CPU 0 is interrupted by a softirq (e.g., TCP URG packet reception). 4. The softirq calls send_sigurg() and attempts to acquire read_lock(&tasklist_lock), deadlocking because CPU 1 is waiting. Since PID hashing and do_each_pid_task() traversals are already RCU-protected, the read_lock on tasklist_lock is no longer strictly required for safe traversal. Fix this by replacing tasklist_lock with rcu_read_lock(), aligning the process group signaling path with the single-PID path. This also mitigates a potential remote denial of service vector via TCP URG packets. Lockdep splat: ===================================================== WARNING: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected [...] Chain exists of: &dev->event_lock --> &f_owner->lock --> tasklist_lock Possible interrupt unsafe locking scenario: CPU0 CPU1 ---- ---- lock(tasklist_lock); local_irq_disable(); lock(&dev->event_lock); lock(&f_owner->lock); <Interrupt> lock(&dev->event_lock); *** DEADLOCK ***
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.47% · top 59% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 54626335ea4174ab2d9a183b511d825f6765e47b
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 897d6a7247739fb1528f98c575df4f2e5de7f994
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 32dbd5ce4be3a3ed7e00f8af18795cc84fc50a33
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b5fa9e32fb6718f70c986ee14dd5d01b4846f331
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1bee417678f1135e35b25a37734db46aa94258d2
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 20a93e397abe850c49b6fa0e8cc827b5f634a8f5
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < bfcc8e8d8a495bb34cae9e620adfb75fb13a3954
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 36c1b57b2ecf3c61ac93f5f07bd29b6f21e226ed
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 00633c4683828acd5256fa8d5163f440d74bbe71
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.259 – ≤ 5.10.*
- unaffected 5.15.210 – ≤ 5.15.*
- unaffected 6.1.176 – ≤ 6.1.*
- unaffected 6.6.143 – ≤ 6.6.*
- unaffected 6.12.94 – ≤ 6.12.*
- unaffected 6.18.36 – ≤ 6.18.*
- unaffected 7.0.13 – ≤ 7.0.*
- unaffected 7.1.1 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References12
- https://git.kernel.org/stable/c/54626335ea4174ab2d9a183b511d825f6765e47b (opens in a new tab)
- https://git.kernel.org/stable/c/897d6a7247739fb1528f98c575df4f2e5de7f994 (opens in a new tab)
- https://git.kernel.org/stable/c/32dbd5ce4be3a3ed7e00f8af18795cc84fc50a33 (opens in a new tab)
- https://git.kernel.org/stable/c/b5fa9e32fb6718f70c986ee14dd5d01b4846f331 (opens in a new tab)
- https://git.kernel.org/stable/c/1bee417678f1135e35b25a37734db46aa94258d2 (opens in a new tab)
- https://git.kernel.org/stable/c/20a93e397abe850c49b6fa0e8cc827b5f634a8f5 (opens in a new tab)
- https://git.kernel.org/stable/c/bfcc8e8d8a495bb34cae9e620adfb75fb13a3954 (opens in a new tab)
- https://git.kernel.org/stable/c/36c1b57b2ecf3c61ac93f5f07bd29b6f21e226ed (opens in a new tab)
- https://git.kernel.org/stable/c/00633c4683828acd5256fa8d5163f440d74bbe71 (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-38814 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-52946)Record last updated .