CVE-2026-53327: Linux kernel · debugobjects: Do not fill_pool() if pi_blocked_on
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-53327 (opens in a new tab)
- git.kernel.org/stable/c/33bee10644f8fff3b1a0187ad5ad34513e5e8e72 (opens in a new tab)
- git.kernel.org/stable/c/3a408cae608d9c075dd3a9e5cfc03b3cb0726863 (opens in a new tab)
- git.kernel.org/stable/c/3f6a3b24ab7b9d51f6f4778254bef0e5847beb55 (opens in a new tab)
- git.kernel.org/stable/c/5f41161059fd0f1bbf18c90f3180e38cc45a14eb (opens in a new tab)
- git.kernel.org/stable/c/8a680d54f1adf3e3aa815578684556716fda6f0c (opens in a new tab)
- git.kernel.org/stable/c/a3383df76f0d7a597066df018409eb9e5e698064 (opens in a new tab)