CVE-2026-53327

published 1 Jul 2026 · updated 8 Nov 2026

debugobjects: Do not fill_pool() if pi_blocked_on

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.1.177, Kernel 6.18.37, Kernel 7.0.13 and 8 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5.15 <6.1.177, >=6.13 <6.18.37, >=6.19 <7.0.13, >=6.2 <6.6.144, >=6.7 <6.12.95, =7.1, >=4bedcc28469a24fe481a8a31b3584e6070457ddb <3a408cae608d9c075dd3a9e5cfc03b3cb0726863, >=4bedcc28469a24fe481a8a31b3584e6070457ddb <3f6a3b24ab7b9d51f6f4778254bef0e5847beb55, >=4bedcc28469a24fe481a8a31b3584e6070457ddb <5f41161059fd0f1bbf18c90f3180e38cc45a14eb, >=4bedcc28469a24fe481a8a31b3584e6070457ddb <8a680d54f1adf3e3aa815578684556716fda6f0c, >=4bedcc28469a24fe481a8a31b3584e6070457ddb <a3383df76f0d7a597066df018409eb9e5e698064, =5.15, >=4bedcc28469a24fe481a8a31b3584e6070457ddb <33bee10644f8fff3b1a0187ad5ad34513e5e8e726.1.177, 6.18.37, 7.0.13, 6.6.144, 6.12.95, 3a408cae608d9c075dd3a9e5cfc03b3cb0726863, 3f6a3b24ab7b9d51f6f4778254bef0e5847beb55, 5f41161059fd0f1bbf18c90f3180e38cc45a14eb, 8a680d54f1adf3e3aa815578684556716fda6f0c, a3383df76f0d7a597066df018409eb9e5e698064, 33bee10644f8fff3b1a0187ad5ad34513e5e8e72
linux-kernel: Kernel>=5.15.0 <6.1.177, >=6.13.0 <6.18.37, >=6.19.0 <7.0.13, >=6.2.0 <6.6.144, >=6.7.0 <6.12.956.1.177, 6.18.37, 7.0.13, 6.6.144, 6.12.95

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-53327 severity on Zeptric[![CVE-2026-53327](https://zeptric.io/badge/cve/CVE-2026-53327.svg)](https://zeptric.io/cve/CVE-2026-53327)