CVE-2026-53327
Low
No strong exploitation signal.
CVSS base
5.5
MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS — probability of exploitation (30 days)
0.1%
3.0th percentile
CISA KEV
Not listed
Weakness / dates
—
Published 2026-07-01 · modified 2026-07-23
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | N | None |
| Integrity | N | None |
| Availability | H | High |
Timeline
- 2026-07-01 — Published (NVD)
- 2026-07-23 — Last modified (NVD)
Description
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fill_pool() if pi_blocked_on On RT enabled kernels, fill_pool() ends up calling rtlock_lock(), which asserts if current::pi_blocked_on is set, because a task can obviously only block on one lock as otherwise the priority inheritenace chain gets corrupted. Prevent this by expanding the conditional to take current::pi_blocked_on into account.
Affected
References
- https://git.kernel.org/stable/c/33bee10644f8fff3b1a0187ad5ad34513e5e8e72
- https://git.kernel.org/stable/c/3a408cae608d9c075dd3a9e5cfc03b3cb0726863
- https://git.kernel.org/stable/c/3f6a3b24ab7b9d51f6f4778254bef0e5847beb55
- https://git.kernel.org/stable/c/5f41161059fd0f1bbf18c90f3180e38cc45a14eb
- https://git.kernel.org/stable/c/8a680d54f1adf3e3aa815578684556716fda6f0c
- https://git.kernel.org/stable/c/a3383df76f0d7a597066df018409eb9e5e698064