CVE-2026-53327
Published Jul 1, 2026
Modified Jul 4, 2026
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.
EPSS — Exploit Prediction
0.0017
Probability of exploitation
0.07%
Percentile rank
EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.
References
Other 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
Frequently Asked Questions
What is CVE-2026-53327? +
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.
How do I check if I'm vulnerable to CVE-2026-53327? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.