Review reviewHigh

CVE-2026-52946

Linux Linux, linux kernel

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 ca...

CVSS
7.5
EPSS
0.46%
37.2% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.46%
Technical severityCVSS 7.5

Vulnerability overview

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 ca...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 54626335ea4174ab2d9a183b511d825f6765e47b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 897d6a7247739fb1528f98c575df4f2e5de7f994, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 32dbd5ce4be3a3ed7e00f8af18795cc84fc50a33, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b5fa9e32fb6718f70c986ee14dd5d01b4846f331, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1bee417678f1135e35b25a37734db46aa94258d2, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 20a93e397abe850c49b6fa0e8cc827b5f634a8f5, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bfcc8e8d8a495bb34cae9e620adfb75fb13a3954, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 36c1b57b2ecf3c61ac93f5f07bd29b6f21e226ed, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 00633c4683828acd5256fa8d5163f440d74bbe71, >= 2.6.12, >= 2.6.12.1 < 5.10.259, >= 5.11 < 5.15.210, >= 5.16 < 6.1.176, >= 6.2 < 6.6.143, >= 6.7 < 6.12.94, >= 6.13 < 6.18.36, >= 6.19 < 7.0.13, >= 7.1 < 7.1.1, 2.6.12
Fixed versions
5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13, 7.1.1

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE
CWE-667
CVE-2026-52946 — Linux Linux, linux kernel | SECUFOCUS NOW